Proximity-based control of media devices for media presentations

ABSTRACT

Embodiments relate generally to electrical/electronic hardware, computer software, wired and wireless network communications, portable, wearable, and stationary media devices. RF transceivers and/or audio system in each media device may be used to wirelessly communicate between media devices and allow configuration and other data to be wirelessly transmitted from one media device to another media device. The proximity detection system may be configured to detect a presence of a user or multiple users and upon detecting presence, access content on a user device, and record the content while also playing back the content on the media device. One or more user devices in proximity of the media device post detection may wirelessly communicate with the media device and the media device may orchestrate handling and/or queuing of content from those devices or from a wirelessly accessible location such as the Cloud, Internet, NAS, Flash memory, or other wireless sources.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation-In-Part of pending U.S. patentapplication Ser. No. 13/831,422, filed on Mar. 14, 2013, and titled“Proximity-Based Control Of Media Devices”, which is herein incorporatedby reference in its entirety for all purposes.

FIELD

Embodiments of the present application relate generally to electricaland electronic hardware, computer software, wired and wireless networkcommunications, wearable, hand held, and portable computing devices forfacilitating communication of information. More specifically, disclosedare media devices that detect proximity of users and/or user devices andtake actions and handle content after detecting presence of users and/oruser devices

BACKGROUND

Conventional paradigms for media devices require a user to take someaction using a finger press to a touch screen or press a button, or thelike, in order to initiate some function on the device, such aslistening to music, for example. Conventional media devices are notconfigured to recognize and act on user preferences as to how the mediadevice serves the user's needs based on changing circumstances andchanging environments the user and media device are subject to.Furthermore, conventional media devices are typically personal devicesthat are mostly if not always used solely by the user and are thereforenot well adapted to servicing the needs of friends, guests, or the likewho may want to share content on their devices with the user.

Thus, there is a need for devices, systems, methods, and software thatallow a user to configure (e.g., wirelessly) a media device to detect auser's presence, take an action based on the user's presence, and allowfor content from a user device or many devices to be handled based ontheir proximity to the media device.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments or examples (“examples”) of the present applicationare disclosed in the following detailed description and the accompanyingdrawings. The drawings are not necessarily to scale:

FIG. 1 depicts a block diagram of one example of a media deviceaccording to an embodiment of the present application;

FIG. 2A depicts one example of a configuration scenario for a userdevice and a media device according to an embodiment of the presentapplication;

FIG. 2B depicts example scenarios for another media device beingconfigured using a configuration from a previously configured mediadevice according to an embodiment of the present application;

FIG. 3 depicts one example of a flow diagram of a process for installingan application on a user device and configuring a first media deviceusing the application according to an embodiment of the presentapplication;

FIGS. 4A and 4B depict example flow diagrams for processes forconfiguring an un-configured media device according to embodiments ofthe present application;

FIG. 5 depicts a profile view of one example of a media device includingcontrol elements and proximity detection islands according toembodiments of the present application;

FIG. 6 depicts a block diagram of one example of a proximity detectionisland according to embodiments of the present application;

FIG. 7 depicts a top plan view of different examples of proximitydetection island configurations according to embodiments of the presentapplication;

FIG. 8A is a top plan view depicting an example of proximity detectionisland coverage according to embodiments of the present application;

FIG. 8B is a front side view depicting an example of proximity detectionisland coverage according to embodiments of the present application;

FIG. 8C is a side view depicting an example of proximity detectionisland coverage according to embodiments of the present application;

FIG. 9 is a top plan view of a media device including proximitydetection islands configured to detect presence according to embodimentsof the present application;

FIG. 10 depicts one example of a flow for presence detection,notification, and media device readiness according to embodiments of thepresent application;

FIG. 11 depicts another example of a flow for presence detection,notification, and media device readiness according to embodiments of thepresent application;

FIG. 12 depicts yet another example of a flow for presence detection,notification, and media device readiness according to embodiments of thepresent application;

FIG. 13 depicts one example of presence detection using proximitydetection islands and/or other systems responsive to wireless detectionof different users and/or different user devices according toembodiments of the present application;

FIG. 14 depicts one example of proximity detection islands associatedwith specific device functions according to embodiments of the presentapplication;

FIG. 15 depicts one example of content handling from a user devicesubsequent to proximity detection according to embodiments of thepresent application;

FIG. 16 depicts another example of content handling from user devicessubsequent to proximity detection according to embodiments of thepresent application;

FIG. 17 depicts one example of content handling from a data capablewristband or wristwatch subsequent to proximity detection according toembodiments of the present application;

FIG. 18 depicts another example of content handling from a data capablewristband or wristwatch subsequent to proximity detection according toembodiments of the present application;

FIG. 19 depicts one example of a flow for content handling on a mediadevice post proximity detection according to embodiments of the presentapplication;

FIG. 20 depicts one example of a flow for storing, recording, andqueuing content post proximity detection according to embodiments of thepresent application;

FIG. 21 depicts one example of a media device handling, storing,queuing, and taking action on content from a plurality of user devicesaccording to embodiments of the present application;

FIG. 22 depicts another example of a media device handling, storing,queuing, and taking action on content from a plurality of user devicesaccording to embodiments of the present application;

FIG. 23 depicts one example of a flow for recording user content on amedia device while the media device handles current content according toembodiments of the present application;

FIG. 24 depicts one example of queuing action for user content in aqueue of a media player according to embodiments of the presentapplication;

DETAILED DESCRIPTION

Various embodiments or examples may be implemented in numerous ways,including as a system, a process, a method, an apparatus, a userinterface, or a series of program instructions on a non-transitorycomputer readable medium such as a computer readable storage medium or acomputer network where the program instructions are sent over optical,electronic, or wireless communication links. In general, operations ofdisclosed processes may be performed in an arbitrary order, unlessotherwise provided in the claims.

A detailed description of one or more examples is provided below alongwith accompanying figures. The detailed description is provided inconnection with such examples, but is not limited to any particularexample. The scope is limited only by the claims and numerousalternatives, modifications, and equivalents are encompassed. Numerousspecific details are set forth in the following description in order toprovide a thorough understanding. These details are provided for thepurpose of example and the described techniques may be practicedaccording to the claims without some or all of these specific details.For clarity, technical material that is known in the technical fieldsrelated to the examples has not been described in detail to avoidunnecessarily obscuring the description.

FIG. 1 depicts a block diagram of one embodiment of a media device 100having systems including but not limited to a controller 101, a datastorage (DS) system 103, a input/output (I/O) system 105, a radiofrequency (RF) system 107, an audio/video (NV) system 109, a powersystem 111, and a proximity sensing (PROX) system 113. A bus 110 enableselectrical communication between the controller 101, DS system 103, I/Osystem 105, RF system 107, AV system 109, power system 111, and PROXsystem 113. Power bus 112 supplies electrical power from power system111 to the controller 101, DS system 103, I/O system 105, RF system 107,AV system 109, and PROX system 113.

Power system 111 may include a power source internal to the media device100 such as a battery (e.g., AAA or AA batteries) or a rechargeablebattery (e.g., such as a lithium ion or nickel metal hydride typebattery, etc.) denoted as BAT 135. Power system 111 may be electricallycoupled with a port 114 for connecting an external power source (notshown) such as a power supply that connects with an external AC or DCpower source. Examples include but are not limited to a wall wart typeof power supply that converts AC power to DC power or AC power to ACpower at a different voltage level. In other examples, port 114 may be aconnector (e.g., an IEC connector) for a power cord that plugs into anAC outlet or other type of connecter, such as a universal serial bus(USB) connector. Power system 111 provides DC power for the varioussystems of media device 100. Power system 111 may convert AC or DC powerinto a form usable by the various systems of media device 100. Powersystem 111 may provide the same or different voltages to the varioussystems of media device 100. In applications where a rechargeablebattery is used for BAT 135, the external power source may be used topower the power system 111, recharge BAT 135, or both. Further, powersystem 111 on its own or under control or controller 101 may beconfigured for power management to reduce power consumption of mediadevice 100, by for example, reducing or disconnecting power from one ormore of the systems in media device 100 when those systems are not inuse or are placed in a standby or idle mode. Power system 111 may alsobe configured to monitor power usage of the various systems in mediadevice 100 and to report that usage to other systems in media device 100and/or to other devices (e.g., including other media devices 100) usingone or more of the I/O system 105, RF system 107, and AV system 109, forexample. Operation and control of the various functions of power system111 may be externally controlled by other devices (e.g., including othermedia devices 100).

Controller 101 controls operation of media device 100 and may include anon-transitory computer readable medium, such as executable program codeto enable control and operation of the various systems of media device100. DS 103 may be used to store executable code used by controller 101in one or more data storage mediums such as ROM, RAM, SRAM, RAM, SSD,Flash, etc., for example. Controller 101 may include but is not limitedto one or more of a microprocessor (μP), a microcontroller (μP), adigital signal processor (DSP), a baseband processor, an applicationspecific integrated circuit (ASIC), just to name a few. Processors usedfor controller 101 may include a single core or multiple cores (e.g.,dual core, quad core, etc.). Port 116 may be used to electrically couplecontroller 101 to an external device (not shown).

DS system 103 may include but is not limited to non-volatile memory(e.g., Flash memory), SRAM, DRAM, ROM, SSD, just to name a few. In thatthe media device 100 in some applications is designed to be compact,portable, or to have a small size footprint, memory in DS 103 willtypically be solid state memory (e.g., no moving or rotatingcomponents); however, in some application a hard disk drive (HDD) orhybrid HDD may be used for all or some of the memory in DS 103. In someexamples, DS 103 may be electrically coupled with a port 128 forconnecting an external memory source (e.g., USB Flash drive, SD, SDHC,SDXC, microSD, Memory Stick, CF, SSD, etc.). Port 128 may be a USB ormini USB port for a Flash drive or a card slot for a Flash memory card.In some examples as will be explained in greater detail below, DS 103includes data storage for configuration data, denoted as CFG 125, usedby controller 101 to control operation of media device 100 and itsvarious systems. DS 103 may include memory designate for use by othersystems in media device 100 (e.g., MAC addresses for WiFi 130, networkpasswords, data for settings and parameters for NV 109, and other datafor operation and/or control of media device 100, etc.). DS 103 may alsostore data used as an operating system (OS) for controller 101. Ifcontroller 101 includes a DSP, then DS 103 may store data, algorithms,program code, an OS, etc. for use by the DSP, for example. In someexamples, one or more systems in media device 100 may include their owndata storage systems.

I/O system 105 may be used to control input and output operationsbetween the various systems of media device 100 via bus 110 and betweensystems external to media device 100 via port 118. Port 118 may be aconnector (e.g., USB, HDMI, Ethernet, fiber optic, Toslink, Firewire,IEEE 1394, or other) or a hard wired (e.g., captive) connection thatfacilitates coupling I/O system 105 with external systems. In someexamples port 118 may include one or more switches, buttons, or thelike, used to control functions of the media device 100 such as a powerswitch, a standby power mode switch, a button for wireless pairing, anaudio muting button, an audio volume control, an audio mute button, abutton for connecting/disconnecting from a WiFi network, an infrared(IR) transceiver, just to name a few. I/O system 105 may also controlindicator lights, audible signals, or the like (not shown) that givestatus information about the media device 100, such as a light toindicate the media device 100 is powered up, a light to indicate themedia device 100 is in wireless communication (e.g., WiFi, Bluetooth®,WiMAX, cellular, etc.), a light to indicate the media device 100 isBluetooth® paired, in Bluetooth® pairing mode, Bluetooth® communicationis enabled, a light to indicate the audio and/or microphone is muted,just to name a few. Audible signals may be generated by the I/O system105 or via the AV system 107 to indicate status, etc. of the mediadevice 100. Audible signals may be used to announce Bluetooth® status,powering up or down the media device 100, muting the audio ormicrophone, an incoming phone call, a new message such as a text, email,or SMS, just to name a few. In some examples, I/O system 105 may useoptical technology to wirelessly communicate with other media devices100 or other devices. Examples include but are not limited to infrared(IR) transmitters, receivers, transceivers, an IR LED, and an IRdetector, just to name a few. I/O system 105 may include an opticaltransceiver OPT 185 that includes an optical transmitter 185 t (e.g., anIR LED) and an optical receiver 185 r (e.g., a photo diode). OPT 185 mayinclude the circuitry necessary to drive the optical transmitter 185 twith encoded signals and to receive and decode signals received by theoptical receiver 185 r. Bus 110 may be used to communicate signals toand from OPT 185. OPT 185 may be used to transmit and receive IRcommands consistent with those used by infrared remote controls used tocontrol AV equipment, televisions, computers, and other types of systemsand consumer electronics devices. The IR commands may be used to controland configure the media device 100, or the media device 100 may use theIR commands to configure/re-configure and control other media devices orother user devices, for example.

RF system 107 includes at least one RF antenna 124 that is electricallycoupled with a plurality of radios (e.g., RF transceivers) including butnot limited to a Bluetooth® (BT) transceiver 120, a WiFi transceiver 130(e.g., for wireless communications over a wireless and/or WiMAXnetwork), and a proprietary Ad Hoc (AH) transceiver 140 pre-configured(e.g., at the factory) to wirelessly communicate with a proprietary AdHoc wireless network (AH-WiFi) (not shown). AH 140 and AH-WiFi areconfigured to allow wireless communications between similarly configuredmedia devices (e.g., an ecosystem comprised of a plurality of similarlyconfigured media devices) as will be explained in greater detail below.RF system 107 may include more or fewer radios than depicted in FIG. 1and the number and type of radios will be application dependent.Furthermore, radios in RF system 107 need not be transceivers, RF system107 may include radios that transmit only or receive only, for example.Optionally, RF system 107 may include a radio 150 configured for RFcommunications using a proprietary format, frequency band, or otherexistent now or to be implemented in the future. Radio 150 may be usedfor cellular communications (e.g., 3G, 4G, or other), for example.Antenna 124 may be configured to be a de-tunable antenna such that itmay be de-tuned 129 over a wide range of RF frequencies including butnot limited to licensed bands, unlicensed bands, WiFi, WiMAX, cellularbands, Bluetooth®, from about 2.0 GHz to about 6.0 GHz range, andbroadband, just to name a few. As will be discussed below, PROX system113 may use the de-tuning 129 capabilities of antenna 124 to senseproximity of the user, other people, the relative locations of othermedia devices 100, just to name a few. Radio 150 (e.g., a transceiver)or other transceiver in RF 107, may be used in conjunction with thede-tuning capabilities of antenna 124 to sense proximity, to detect andor spatially locate other RF sources such as those from other mediadevices 100, devices of a user, just to name a few. RF system 107 mayinclude a port 123 configured to connect the RF system 107 with anexternal component or system, such as an external RF antenna, forexample. The transceivers depicted in FIG. 1 are non-limiting examplesof the type of transceivers that may be included in RF system 107. RFsystem 107 may include a first transceiver configured to wirelesslycommunicate using a first protocol, a second transceiver configured towirelessly communicate using a second protocol, a third transceiverconfigured to wirelessly communicate using a third protocol, and so on.One of the transceivers in RF system 107 may be configured for shortrange RF communications, such as within a range from about 1 meter toabout 15 meters, or less, for example. Another one of the transceiversin RF system 107 may be configured for long range RF communications,such any range up to about 50 meters or more, for example. Short rangeRF may include Bluetooth®; whereas, long range RF may include WiFi,WiMAX, cellular, and Ad Hoc wireless, for example.

AV system 109 includes at least one audio transducer, such as a loudspeaker 160, a microphone 170, or both. AV system 109 further includescircuitry such as amplifiers, preamplifiers, or the like as necessary todrive or process signals to/from the audio transducers. Optionally, AVsystem 109 may include a display (DISP) 180, video device (VID) 190(e.g., an image captured device or a web CAM, etc.), or both. DISP 180may be a display and/or touch screen (e.g., a LCD, OLED, or flat paneldisplay) for displaying video media, information relating to operationof media device 100, content available to or operated on by the mediadevice 100, playlists for media, date and/or time of day, alpha-numerictext and characters, caller ID, file/directory information, a GUI, justto name a few. A port 122 may be used to electrically couple AV system109 with an external device and/or external signals. Port 122 may be aUSB, HDMI, Firewire/IEEE-1394, 3.5 mm audio jack, or other. For example,port 122 may be a 3.5 mm audio jack for connecting an external speaker,headphones, earphones, etc. for listening to audio content beingprocessed by media device 100. As another example, port 122 may be a 3.5mm audio jack for connecting an external microphone or the audio outputfrom an external device. In some examples, SPK 160 may include but isnot limited to one or more active or passive audio transducers such aswoofers, concentric drivers, tweeters, super tweeters, midrange drivers,sub-woofers, passive radiators, just to name a few. MIC 170 may includeone or more microphones and the one or more microphones may have anypolar pattern suitable for the intended application including but notlimited to omni-directional, directional, bi-directional,uni-directional, bi-polar, uni-polar, any variety of cardioid pattern,and shotgun, for example. MIC 170 may be configured for mono, stereo, orother. MIC 170 may be configured to be responsive (e.g., generate anelectrical signal in response to sound) to any frequency range includingbut not limited to ultrasonic, infrasonic, from about 20 Hz to about 20kHz, and any range within or outside of human hearing. In someapplications, the audio transducer of AV system 109 may serve dual rolesas both a speaker and a microphone.

Circuitry in AV system 109 may include but is not limited to adigital-to-analog converter (DAC) and algorithms for decoding andplayback of media files such as MP3, FLAG, AIFF, ALAC, WAV, MPEG,QuickTime, AVI, compressed media files, uncompressed media files, andlossless media files, just to name a few, for example. A DAC may be usedby AV system 109 to decode wireless data from a user device or from anyof the radios in RF system 107. AV system 109 may also include ananalog-to-digital converter (ADC) for converting analog signals, fromMIC 170 for example, into digital signals for processing by one or moresystem in media device 100.

Media device 100 may be used for a variety of applications including butnot limited to wirelessly communicating with other wireless devices,other media devices 100, wireless networks, and the like for playback ofmedia (e.g., streaming content), such as audio, for example. The actualsource for the media need not be located on a user's device (e.g., smartphone, MP3 player, iPod, iPhone, iPad, Android, laptop, PC, etc.). Forexample, media files to be played back on media device 100 may belocated on the Internet, a web site, or in the Cloud, and media device100 may access (e.g., over a WiFi network via WiFi 130) the files,process data in the files, and initiate playback of the media files.Media device 100 may access or store in its memory a playlist orfavorites list and playback content listed in those lists. In someapplications, media device 100 will store content (e.g., files) to beplayed back on the media device 100 or on another media device 100.

Media device 100 may include a housing, a chassis, an enclosure or thelike, denoted in FIG. 1 as 199. The actual shape, configuration,dimensions, materials, features, design, ornamentation, aesthetics, andthe like of housing 199 will be application dependent and a matter ofdesign choice. Therefore, housing 199 need not have the rectangular formdepicted in FIG. 1 or the shape, configuration etc., depicted in theDrawings of the present application. Nothing precludes housing 199 fromcomprising one or more structural elements, that is, the housing 199 maybe comprised of several housings that form media device 100. Housing 199may be configured to be worn, mounted, or otherwise connected to orcarried by a human being. For example, housing 199 may be configured asa wristband, an earpiece, a headband, a headphone, a headset, anearphone, a hand held device, a portable device, a desktop device, justto name a few.

In other examples, housing 199 may be configured as speaker, asubwoofer, a conference call speaker, an intercom, a media playbackdevice, just to name a few. If configured as a speaker, then the housing199 may be configured as a variety of speaker types including but notlimited to a left channel speaker, a right channel speaker, a centerchannel speaker, a left rear channel speaker, a right rear channelspeaker, a subwoofer, a left channel surround speaker, a right channelsurround speaker, a left channel height speaker, a right channel heightspeaker, any speaker in a 3.1, 5.1, 7.1, 9.1 or other surround soundformat including those having two or more subwoofers or having two ormore center channels, for example. In other examples, housing 199 may beconfigured to include a display (e.g., DISP 180) for viewing video,serving as a touch screen interface for a user, providing an interfacefor a GUI, for example.

PROX system 113 may include one or more sensors denoted as SEN 195 thatare configured to sense 197 an environment 198 external to the housing199 of media device 100. Using SEN 195 and/or other systems in mediadevice 100 (e.g., antenna 124, SPK 160, MIC 170, etc.), PROX system 113senses 197 an environment 198 that is external to the media device 100(e.g., external to housing 199). PROX system 113 may be used to senseone or more of proximity of the user or other persons to the mediadevice 100 or other media devices 100. PROX system 113 may use a varietyof sensor technologies for SEN 195 including but not limited toultrasound, infrared (IR), passive infrared (PIR), optical, acoustic,vibration, light, ambient light sensor (ALS), IR proximity sensors, LEDemitters and detectors, RGB LED's, RF, temperature, capacitive,capacitive touch, inductive, just to name a few. PROX system 113 may beconfigured to sense location of users or other persons, user devices,and other media devices 100, without limitation. Output signals fromPROX system 113 may be used to configure media device 100 or other mediadevices 100, to re-configure and/or re-purpose media device 100 or othermedia devices 100 (e.g., change a role the media device 100 plays forthe user, based on a user profile or configuration data), just to name afew. A plurality of media devices 100 in an eco-system of media devices100 may collectively use their respective PROX system 113 and/or othersystems (e.g., RF 107, de-tunable antenna 124, AV 109, etc.) toaccomplish tasks including but not limited to changing configuration,re-configuring one or more media devices, implement user specifiedconfigurations and/or profiles, insertion and/or removal of one or moremedia devices in an eco-system, just to name a few.

In other examples, PROX 113 may include one or more proximity detectionislands PSEN 520 as will be discussed in greater detail in FIGS. 5-6.PSEN 520 may be positioned at one or more locations on chassis 199 andconfigured to sense an approach of a user or other person towards themedia device 100 or to sense motion or gestures of a user or otherperson by a portion of the body such as a hand for example. PSEN 520 maybe used in conjunction with or in place of one or more of SEN 195, OPT185, SPK 160, MIC 170, RF 107 and/or de-tunable 129 antenna 124 to senseproximity and/or presence in an environment surrounding the media device100, for example. PSEN 520 may be configured to take or cause an actionto occur upon detection of an event (e.g., an approach or gesture byuser 201 or other) such as emitting light (e.g., via an LED), generatinga sound or announcement (e.g., via SPK 160), causing a vibration (e.g.,via SPK 160 or a vibration motor), display information (e.g., via DISP180), trigger haptic feedback, for example. In some examples, PSEN 520may be included in I/O 105 instead of PROX 113 or be shared between oneor more systems of media device 100. In other examples, components,circuitry, and functionality of PSEN 520 may vary among a plurality ofPSEN 520 sensors in media device 100 such that all PSEN 520 are notidentical.

Simple Out-of-the-Box User Experience

Attention is now directed to FIG. 2A, where a scenario 200 a depicts oneexample of a media device (e.g., media device 100 of FIG. 1 or asimilarly provisioned media device) being configured for the first timeby a user 201. For purposes of explanation, in FIG. 2A media device isdenoted as 100 a to illustrate that it is the first time the mediadevice 100 a is being configured. For example, the first configurationof media device 100 a may be after it is purchased, acquired, borrowed,or otherwise by user 201, that is, the first time may be the initialout-of-the-box configuration of media device 100 a when it is new.Scenario 200 a depicts a desirable user experience for user 201 toachieve the objective of making the configuring of media device 100 a aseasy, straight forward, and fast as possible.

To that end, in FIG. 2A, scenario 200 a may include media device 100 ato be configured, for example, initially by user 201 using a variety ofdevices 202 including but not limited to a smartphone 210, a tablet 220,a laptop computer 230, a data capable wristband or the like 240, adesktop PC or server 250, . . . etc. For purposes of simplifyingexplanation, the following description will focus on tablet 220,although the description may apply to any of the other devices 202 aswell. Upon initial power up of media device 100 a, controller 101 maycommand RF system 107 to electrically couple 224, transceiver BT 120with antenna 124, and command BT 120 to begin listening 126 for a BTpairing signal from device 220. Here, user 201 as part of theinitialization process may have already used a Bluetooth® menu on tablet220 to activate the BT radio and associated software in tablet 220 tobegin searching (e.g., via RF) for a BT device to pair with. Pairing mayrequire a code (e.g., a PIN number or code) be entered by the user 201for the device being paired with, and the user 201 may enter a specificcode or a default code such as “0000”, for example.

Subsequently, after tablet 220 and media device 100 a have successfullyBT paired with one another, the process of configuring media device 100a to service the specific needs of user 201 may begin. In some examples,after successful BT pairing, BT 120 need not be used for wirelesscommunication between media device 100 a and the user's device (e.g.,tablet 220 or other). Controller 101, after a successful BT pairing, maycommand RF system 107 to electrically couple 228, WiFi 130 with antenna124 and wireless communications between tablet 220 and media device 100a (see 260, 226) may occur over a wireless network (e.g., WiFi or WiMAX)or other as denoted by wireless access point 270. Post-pairing, tablet220 requires a non-transitory computer readable medium that includesdata and/or executable code to form a configuration (CFG) 125 for mediadevice 100 a. For purposes of explanation, the non-transitory computerreadable medium will be denoted as an application (APP) 225. APP 225resides on or is otherwise accessible by tablet 220 or media device 100a. User 201 uses APP 225 (e.g., through a GUI, menu, drop down boxes, orthe like) to make selections that comprise the data and/or executablecode in the CFG 125.

APP 225 may be obtained by tablet 220 in a variety of ways. In oneexample, the media device 100 a includes instructions (e.g., on itspackaging or in a user manual) for a website on the Internet 250 wherethe APP 225 may be downloaded. Tablet 220 may use its WiFi or CellularRF systems to communicate with wireless access point 270 (e.g., a celltower or wireless router) to connect 271 with the website and downloadAPP 255 which is stored on tablet 220 as APP 225. In another example,tablet 220 may scan or otherwise image a bar code or TAG operative toconnect the tablet 220 with a location (e.g., on the Internet 250) wherethe APP 225 may be found and downloaded. Tablet 220 may have access toan applications store such as Google Play for Android devices, the AppleApp Store for iOS devices, or the Windows 8 App Store for Windows 8devices. The APP 225 may then be downloaded from the app store. In yetanother example, after pairing, media device 100 a may be preconfiguredto either provide (e.g., over the BT 120 or WiFi 130) an address orother location that is communicated to tablet 220 and the tablet 220uses the information to locate and download the APP 225. In anotherexample, media device 100 a may be preloaded with one or more versionsof APP 225 for use in different device operating systems (OS), such asone version for Android, another for iOS, and yet another for Windows 8,etc. In that OS versions and/or APP 225 are periodically updated, mediadevice 100 a may use its wireless systems (e.g., BT 120 or WiFi 130) todetermine if the preloaded versions are out of date and need to bereplaced with newer versions, which the media device 100 a obtains,downloads, and subsequently makes available for download to tablet 220.

Regardless of how the APP 225 is obtained, once the APP 225 is installedon any of the devices 202, the user 201 may use the APP 225 to selectvarious options, commands, settings, etc. for CFG 125 according to theuser's preferences, needs, media device ecosystem, etc., for example.After the user 201 finalizes the configuration process, CFG 125 isdownloaded (e.g., using BT 120 or WiFi 130) into DS system 103 in mediadevice 100 a. Controller 101 may use the CFG 125 and/or other executablecode to control operation of media device 100 a. In FIG. 2A, the sourcefor APP 225 may be obtained from a variety of locations including butnot limited to: the Internet 250; a file or the like stored in theCloud; a web site; a server farm; a FTP site; a drop box; an app store;a manufactures web site; or the like, just to name a few. APP 225 may beinstalled using other processes including but not limited to: draggingand dropping the appropriate file into a directory, folder, desktop orthe like on tablet 220; emailing the APP 225 as an attachment, acompressed or ZIP file; cutting and pasting the App 225, just to name afew.

CFG 125 may include data such as the name and password for a wirelessnetwork (e.g., 270) so that WiFi 130 may connect with (see 226) and usethe wireless network for future wireless communications, data forconfiguring subsequently purchased devices 100, data to access media forplayback, just to name a few. By using the APP 225, user 201 may updateCFG 125 as the needs of the user 201 change over time, that is, APP 225may be used to re-configure an existing CFG 125. Furthermore, APP 225may be configured to check for updates and to query the user 201 toaccept the updates such that if an update is accepted an updated versionof the APP 225 may be installed on tablet 220 or on any of the otherdevices 202. Although the previous discussion has focused on installingthe APP 225 and CFG 125, one skilled in the art will appreciate thatother data may be installed on devices 202 and/or media device 100 ausing the process described above. As one example, APP 225 or some otherprogram may be used to perform software, firmware, or data updates ondevice 100 a. DS system 103 on device 100 a may include storage setaside for executable code (e.g., an operating system) and data used bycontroller 101 and/or the other systems depicted in FIG. 1.

Moving on to FIG. 2B, where a several example scenarios of how apreviously configured media device 100 a that includes CFG 125 may beused to configure another media device 100 b that is initiallyun-configured. In scenario 200 b, media device 100 a is already poweredup or is turned on (e.g., by user 201) or is otherwise activated suchthat its RF system 107 is operational. Accordingly, at stage 290 a,media device 100 a is powered up and configured to detect RF signaturesfrom other powered up media devices using its RF system 107. At stage290 b another media device denoted as 100 b is introduced into RFproximity of media device 100 a and is powered up so that its RF system107 is operational and configured to detect RF signatures from otherpowered up media devices (e.g., signature of media device 100 a). HereRF proximity broadly means within adequate signal strength range of theBT transceivers 120, WiFi transceivers 130, or any other transceivers inRF system 107, RF systems in the users devices (e.g., 202, 220), andother wireless devices such as wireless routers, WiFi networks (e.g.,270), WiMAX networks, and cellular networks, for example. Adequatesignal strength range is any range that allows for reliable RFcommunications between wireless devices. For BT enabled devices,adequate signal strength range may be determined by the BTspecification, but is subject to change as the BT specification andtechnology evolve. For example, adequate signal strength range for BT120 may be approximately 10 meters (e.g., ˜30 feet). For WiFi 130,adequate signal strength range may vary based on parameters such asdistance from and signal strength of the wireless network, andstructures that interfere with the WiFi signal. However, in most typicalwireless systems adequate signal strength range is usually greater than10 meters.

At stage 290 b, media device 100 b is powered up and at stage 290 c itsBT 120 and the BT 120 of media device 100 a recognize each other. Forexample, each media device (100 a, 100 b) may be pre-configured (e.g.,at the factory) to broadcast a unique RF signature or other wirelesssignature (e.g., acoustic) at power up and/or when it detects the uniquesignature of another device. The unique RF signature may include statusinformation including but not limited to the configuration state of amedia device. Each BT 120 may be configured to allow communications withand control by another media device based on the information in theunique RF signature. Accordingly, at the stage 290 c, media device 100 btransmits RF information that includes data that informs other listeningBT 120's (e.g., BT 120 in 100 a) that media device 100 b isun-configured (e.g., has no CFG 125).

At stage 290 d, media devices 100 a and 100 b negotiate the necessaryprotocols and/or handshakes that allow media device 100 a to gain accessto DS 103 of media device 100 b. At stage 290 e, media device 100 b isready to receive CFG 125 from media device 100 a, and at stage 290 f theCFG 125 from media device 100 a is transmitted to media device 100 b andis replicated (e.g., copied, written, etc.) in the DS 103 of mediadevice 100 b, such that media device 100 b becomes a configured mediadevice.

Data in CFG 125 may include information on wireless network 270,including but not limited to wireless network name, wireless password,MAC addresses of other media devices, media specific configuration suchas speaker type (e.g., left, right, center channel), audio mute,microphone mute, etc. Some configuration data may be subservient toother data or dominant to other data. After the stage 290 f, mediadevice 100 a, media device 100 b, and user device 220 may wirelesslycommunicate 291 with one another over wireless network 270 using theWiFi systems of user device 220 and WiFi 130 of media devices 100 a and100 b.

APP 225 may be used to input the above data into CFG 125, for exampleusing a GUI included with the APP 225. User 201 enters data and makesmenu selections (e.g., on a touch screen display) that will become partof the data for the CFG 125. APP 225 may also be used to update and/orre-configure an existing CFG 125 on a configured media device.Subsequent to the update and/or re-configuring, other configured orun-configured media devices in the user's ecosystem may be updatedand/or re-configured by a previously updated and/or re-configured mediadevice as described herein, thereby relieving the user 201 from havingto perform the update and/or re-configure on several media devices. TheAPP 225 or a location provided by the APP 225 may be used to specifyplaylists, media sources, file locations, and the like. APP 225 may beinstalled on more than one user device 202 and changes to APP 225 on oneuser device may later by replicated on the APP 225 on other user devicesby a synching or update process, for example. APP 225 may be stored onthe internet or in the Cloud and any changes to APP 225 may beimplemented in versions of the APP 225 on various user devices 202 bymerely activating the APP 225 on that device and the APP 225 initiates aquery process to see if any updates to the APP are available, and if so,then the APP 225 updates itself to make the version on the user devicecurrent with the latest version.

Media devices 100 a and 100 b having their respective WiFi 130 enabledto communicate with wireless network 270, tablet 220, or other wirelessdevices of user 201. FIG. 2B includes an alternate scenario 200 b thatmay be used to configure a newly added media device, that is, anun-configured media device (e.g., 100 b). For example, at stage 290 d,media device 100 a, which is assumed to already have its WiFi 130configured for communications with wireless network 270, transmits overits BT 120 the necessary information for media device 100 b to joinwireless network 270. After stage 290 d, media device 100 b, mediadevice 100 a, and tablet 220 are connected 291 to wireless network 270and may communicate wirelessly with one another via network 270.Furthermore, at stage 290 d, media device 100 b is still in anun-configured state. Next, at stage 290 e, APP 225 is active on tablet220 and wirelessly accesses the status of media devices 100 a and 100 b.APP 225 determines that media device 100 b is un-configured and APP 225acts to configure 100 b by harvesting CFG 125 (e.g., getting a copy of)from configured media device 100 a by wirelessly 293 a obtaining CFG 125from media device 100 a and wirelessly 293 b transmitting the harvestedCFG 125 to media device 100 b. Media device 100 b uses its copy of CFG125 to configure itself thereby placing it in a configured state.

After all the devices 220, 100 a, 100 b, are enabled for wirelesscommunications with one another, FIG. 2B depicts yet another examplescenario where after stage 290 d, the APP 225 or any one of the mediadevices 100 a, 100 b, may access 295 the CFG 125 for media device 100 bfrom an external location, such as the Internet, the cloud, etc. asdenoted by 250 where a copy of CFG 125 may be located and accessed fordownload into media device 100 b. APP 255, media device 100 b, or mediadevice 100 a, may access the copy of CFG 125 from 250 and wirelesslyinstall it on media device 100 b.

In the example scenarios depicted in FIG. 2B, it should be noted thatafter the pairing of media device 100 a and tablet 220 in FIG. 2A, theconfiguration of media device 100 b in FIG. 2B did not require tablet220 to use its BT features to pair with media device 100 b to effectuatethe configuration of media device 100 b. Moreover, there was no need forthe BT pairing between tablet 220 and media device 100 a to be broken inorder to effectuate the configuration of media device 100 b.Furthermore, there is no need for table 220 and media devices 100 aand/or 100 b to be BT paired at all with tablet 220 in order toconfigure media device 100 b. Accordingly, from the standpoint of user201, adding a new media device to his/her ecosystem of similarlyprovisioned media devices does not require un-pairing with one or morealready configured devices and then pairing with the new device to beadded to the ecosystem. Instead, one of the already configured devices(e.g., media device 100 a having CFG 125 installed) may negotiate withthe APP 225 and/or the new device to be added to handle theconfiguration of the new device (e.g., device 100 b). Similarlyprovisioned media devices broadly means devices including some, all, ormore of the systems depicted in FIG. 1 and designed (e.g., by the samemanufacture or to the same specifications and/or standards) to operatewith one another in a seamless manner as media devices are added to orremoved from an ecosystem.

Reference is now made to FIG. 3 where a flow diagram 300 depicts oneexample of configuring a first media device using an applicationinstalled on a user device as was described above in regards to FIG. 2A.At a stage 302 a Bluetooth® (BT) discovery mode is activated on a userdevice such as the examples 202 of user devices depicted in FIG. 2A.Typically, a GUI on the user device includes a menu for activating BTdiscovery mode, after which, the user device waits to pick up a BTsignal of a device seeking to pair with the user's device. At a stage304 a first media device (e.g., 100 a) is powered up (if not alreadypowered up). At stage 306 a BT pairing mode is activated on the firstmedia device. Examples of activating BT pairing mode include but are notlimited to pushing a button or activating a switch on the first mediadevice that places the first media device in BT pairing mode such thatits BT 120 is activated to generate a RF signal that the user's devicemay discover while in discovery mode. I/O system 105 of media device 100may receive 118 as a signal the activation of BT pairing mode byactuation of the switch or button and that signal is processed bycontroller 101 to command RF system 107 to activate BT 120 in pairingmode. In other examples, after powering up the first media device, adisplay (e.g., DISP 180) may include a touch screen interface and/or GUIthat guides a user to activate the BT pairing mode on the first mediadevice.

At a stage 308 the user's device and the first media device negotiatethe BT pairing process, and if BT pairing is successful, then the flowcontinues at stage 310. If BT pairing is not successful, then the flowrepeats at the stage 206 until successful BT pairing is achieved. Atstage 310 the user device is connected to a wireless network (if notalready connected) such as a WiFi, WiMAX, or cellular (e.g., 3G or 4G)network. At a stage 312, the wireless network may be used to install anapplication (e.g., APP 225) on the user's device. The location of theAPP (e.g., on the Internet or in the Cloud) may be provided with themedia device or after successful BT pairing, the media device may useits BT 120 to transmit data to the user's device and that data includesa location (e.g., a URI or URL) for downloading or otherwise accessingthe APP. At a stage 314, the user uses the APP to select settings for aconfiguration (e.g., CFG 125) for the first media device. After the usercompletes the configuration, at a stage 316 the user's device installsthe APP on the first media device. The installation may occur in avariety of ways (see FIG. 2A) including but not limited to: using the BTcapabilities of each device (e.g., 220 and 100 a) to install the CFG;using the WiFi capabilities of each device to install the CFG; andhaving the first media device (e.g., 100 a) fetch the CFG from anexternal source such as the Internet or Cloud using its WiFi 130; justto name a few. Optionally, at stages 318-324 a determination of whetheror not the first media device is connected with a wireless network maybe made at a stage 318. If the first media device is already connectedwith a wireless network the “YES” branch may be taken and the flow mayterminate at stage 320. On the other hand, if the first media device isnot connected with a wireless network the “NO” branch may be taken andthe flow continues at a stage 322 where data in the CFG is used toconnect WiFi 130 with a wireless network and the flow may terminate at astage 324. The CFG may contain the information necessary for asuccessful connection between WiFi 130 and the wireless network, such aswireless network name and wireless network password, etc.

Now reference is made to FIG. 4A, where a flow diagram 400 a depicts oneexample of a process for configuring an un-configured media device “B”(e.g., un-configured media device 100 b at stage 290 b of FIG. 2B) usinga configured media device “A” (e.g., media device 100 a having CFG 125of FIG. 2B). At a stage 402 an already configured media device “A” ispowered up. At a stage 404 the RF system (e.g., RF system 107 of FIG. 1)of configured media device “A” is activated. The RF system is configuredto detect RF signals from other “powered up” media devices. At a stage406, an un-configured media device “B” (e.g., un-configured media device100 b at stage 290 b of FIG. 2B) is powered up. At a stage 408 the RFsystem of un-configured media device “B” is activated. At stage 408, therespective RF systems of the configured “A” and un-configured “B” mediadevices are configured to recognize each other (e.g., via theirrespective BT 120 transceivers or another transceiver in the RF system).At a stage 410, if the configured “A” and un-configured “B” mediadevices recognize each other, then a “YES” branch is taken to a stage412 where the configured media device “A” transmits its configuration(e.g., CFG 125) to the un-configured media device “B” (e.g., see stages290 e and 290 f in FIG. 2B). If the configured “A” and un-configured “B”media devices do not recognize each other, then a “NO” branch is takenand the flow may return to an earlier stage (e.g., stage 404 to retrythe recognition process. Optionally, after being configured, mediadevice “B” may be connected with a wireless network (e.g., via WiFi130). At a stage 414 a determination is made as to whether or not mediadevice “B” is connected to a wireless network. If already connected,then a “YES” branch is taken and the process may terminate at a stage416. However, if not connected with a wireless network, then a “NO”branch is taken and media device “B” is connected to the wirelessnetwork at a stage 418. For example, the CFG 125 that was copied tomedia device “B” may include information such as wireless network nameand password and WiFi 130 is configured to effectuate the connectionwith the wireless network based on that information. Alternatively,media device “A” may transmit the necessary information to media device“B” (e.g., using BT 120) at any stage of flow 400 a, such as at thestage 408, for example. After the wireless network connection is made,the flow may terminate at a stage 420.

Attention is now directed to FIG. 4B, where a flow diagram 400 b depictsanother example of a process for configuring an un-configured mediadevice “B” (e.g., un-configured media device 100 b at stage 290 b ofFIG. 2B) using a configured media device “A” (e.g., media device 100 ahaving CFG 125 of FIG. 2B). At a stage 422 an already configured mediadevice “A” is powered up. At a stage 424 the RF system of configuredmedia device “A” is activated (e.g., RF system 107 of FIG. 1). The RFsystem is configured to detect RF signals from other “powered up” mediadevices. At a stage 426, an un-configured media device “B” (e.g.,un-configured media device 100 b at stage 290 b of FIG. 2B) is poweredup. At a stage 428 the RF system of un-configured media device “b” isactivated (e.g., RF system 107 of FIG. 1). At the stage 428, therespective RF systems of the configured “A” and un-configured “B” mediadevices are configured to recognize each other (e.g., via theirrespective BT 120 transceivers or another transceiver in the RF system).At a stage 430, if the configured “A” and un-configured “B” mediadevices recognize each other, then a “YES” branch is taken to a stage432 where the configured media device “A” transmits information for awireless network to the un-configured media device “B” (e.g., see stage290 b in FIG. 2B) and that information is used by the un-configuredmedia device “B” to connect with a wireless network as was describedabove in regards to FIGS. 2B and 4A. If the configured “A” andun-configured “B” media devices do not recognize each other, then a “NO”branch is taken and the flow may return to an earlier stage (e.g., stage424 to retry the recognition process. At a stage 434, the informationfor the wireless network is used by the un-configured media device “B”to effectuate a connection to the wireless network. At a stage 436, auser device is connected with the wireless network and an application(APP) running on the user device (e.g., APP 225 in FIG. 2B) isactivated. Stage 436 may be skipped if the user device is alreadyconnected to the wireless network. The APP is aware of un-configuredmedia device “B” presence on the wireless network and at a stage 438detects that media device “B” is presently in an un-configured state andtherefore has a status of “un-configured.” Un-configured media device“B” may include registers, circuitry, data, program code, memoryaddresses, or the like that may be used to determine that the mediadevice is un-configured. The un-configured status of media device “B”may be wirelessly broadcast using any of its wireless resources or othersystems, such as RF 107 and/or AV 109. At a stage 440, the APP is awareof configured media device “A” presence on the wireless network anddetects that media device “A” is presently in a configured state andtherefore has a status of “configured.” The APP harvests theconfiguration (CFG) (e.g., CFG 125 of FIG. 2B) from configured mediadevice “A”, and at a stage 442 copies (e.g., via a wireless transmissionover the wireless network) the CFG to the un-configured media device“B.” At a stage 444, previously un-configured media device “B” becomes aconfigured media device “B” by virtue of having CFG resident in itssystem (e.g., CFG 125 in DS system 103 in FIG. 1). After media device“B” has been configured, the flow may terminate at a stage 446. In otherexamples, the APP may obtain the CFG from a location other than theconfigured media device “A”, such as the Internet or the Cloud asdepicted in FIG. 2B. Therefore, at the stage 440, the APP may downloadthe CFG from a web site, from Cloud storage, or other locations on theInternet or an intranet for example.

In the examples depicted in FIGS. 2A-4B, after one of the media devicesis configured, additional media devices that are added by the user orare encountered by the user may be configured without the user (e.g.,user 201) having to break a BT pairing with one media device and thenestablishing another BT pairing with a media device the user is addingto his/her media device ecosystem. Existing media devices that areconfigured (e.g., have CFG 125) may be used to configure a new mediadevice using the wireless systems (e.g., acoustic, optical, RF) of themedia devices in the ecosystem. If multiple configured media devices arepresent in the ecosystem when the user adds a new un-configured mediadevice, configured media devices may be configured to arbitrate amongthemselves as to which of the configured devices will act to configuredthe newly added un-configured media device. For example, the existingmedia device that was configured last in time (e.g., by a date stamp onits CFG 125) may be the one selected to configure the newly addedun-configured media device. Alternatively, the existing media devicethat was configured first in time (e.g., by a date stamp on its CFG 125)may be the one selected to configure the newly added un-configured mediadevice. The APP 225 on the user device 220 or other, may be configuredto make the configuration process as seamless as possible and may onlyprompt the user 201 that the APP 225 has detected an un-configured mediadevice and query the user 201 as to whether or not the user 201 wantsthe APP 225 to configure the un-configured media device (e.g., mediadevice 100 b). If the user replies “YES”, then the APP 225 may handlethe configuration process working wirelessly with the configured andun-configured media devices. If the user 201 replies “NO”, then the APP225 may postpone the configuration for a later time when the user 201 isprepared to consummate the configuration of the un-configured mediadevice. In other examples, the user 201 may want configuration ofun-configured media devices to be automatic upon detection of theun-configured media device(s). Here the APP and/or configured mediadevices would automatically act to configure the un-configured mediadevice(s).

APP 225 may be configured (e.g., by the user 201) to automaticallyconfigure any newly detected un-configured media devices that are addedto the user's 201 ecosystem and the APP 225 may merely inform the user201 that it is configuring the un-configured media devices and informthe user 201 when configuration is completed, for example. Moreover, inother examples, once a user 201 configures a media device using the APP225, subsequently added un-configured media devices may be automaticallyconfigured by an existing configured media device by each media devicerecognizing other media devices (e.g., via wireless systems),determining the status (e.g., configured or un-configured) of each mediadevice, and then using the wireless systems (e.g., RF 107, AV 109, I/O105, OPT 185, PROX 113) of a configured media device to configure theun-configured media device without having to resort to the APP 225 onthe user's device 220 to intervene in the configuration process. Thatis, the configured media devices and the un-configured media devicesarbitrate and effectuate the configuring of un-configured media deviceswithout the aid of APP 225 or user device 220. In this scenario, thecontroller 101 and/or CFG 125 may include instructions for configuringmedia devices in an ecosystem using one or more systems in the mediadevices themselves.

In at least some examples, the structures and/or functions of any of theabove-described features may be implemented in software, hardware,firmware, circuitry, or in any combination thereof. Note that thestructures and constituent elements above, as well as theirfunctionality, may be aggregated with one or more other structures orelements. Alternatively, the elements and their functionality may besubdivided into constituent sub-elements, if any. As software, theabove-described techniques may be implemented using various types ofprogramming or formatting languages, frameworks, scripts, syntax,applications, protocols, objects, or techniques. As hardware and/orfirmware, the above-described techniques may be implemented usingvarious types of programming or integrated circuit design languages,including hardware description languages, such as any register transferlanguage (“RTL”) configured to design field-programmable gate arrays(“FPGAs”), application-specific integrated circuits (“ASICs”), or anyother type of integrated circuit. According to some embodiments, theterm “module” may refer, for example, to an algorithm or a portionthereof, and/or logic implemented in either hardware circuitry orsoftware, or a combination thereof. These may be varied and are notlimited to the examples or descriptions provided. Software, firmware,algorithms, executable computer readable code, program instructions forexecution on a computer, or the like may be embodied in a non-transitorycomputer readable medium.

Media Device with Proximity Detection

Attention is now directed to FIG. 5 where a profile view depicts oneexample 500 of media device 100 that may include on a top surface 199 sof chassis 199, a plurality of control elements 503-512 and one or moreproximity detection islands (four are depicted) denoted as 520. Mediadevice 100 may include one or more speakers 160, one or more microphones170, a display 180, a section 550 for other functions such as SEN 195,VID 109, or other, and antenna 124 which may be tunable 129. Eachproximity detection island 520 may be configured to detect 597 proximityof one or more persons, such as user 201 as will be described in greaterdetail below. The layout and position of the elements on chassis 199 ofmedia device 100 are examples only and actual layout and position of anyelements will be application specific and/or a matter of design choice,including ergonomic and esthetic considerations. As will be described ingreater detail below, detection of presence of user 201 may occur withor without the presence of one or more user devices 202, such as userdevices 210 and 220 depicted in FIG. 5. Circuitry and/or softwareassociated with operation of proximity detection islands 520 may work inconjunction with other systems in media device 100 to detect presence ofone or more user devices 202, such as RF system 107 detecting RF signals563 and/or 565 (e.g., via antenna 124) from user devices 210 and 220 orMIC 170 detecting sound, for example. Detection of presence may besignaled by media device 100 in a variety of ways including but notlimited to light (e.g., from 520 and/or 503-512), sound (e.g., from SPK160), vibration (e.g., from SPK 160 or other), haptic feedback, tactilefeedback, display of information (e.g., DISP 180), RF transmission(e.g., 126), just to name a few. SPK 160 and DISP 180 may be positionedon a front surface 199 f of chassis 199. A bottom surface 199 b ofchassis 199 may be configured to rest on a surface such as a table,desk, cabinet, or the like. Other elements of media device 100 may bepositioned on a rear surface 199 r of chassis 199.

Non-limiting examples of control elements 503-512 include a plurality ofcontrols 512 (e.g., buttons, switches and/or touch surfaces) that mayhave functions that are fixed or change based on different scenarios aswill be described below, controls 503 and 507 for volume up and volumedown, control 509 for muting volume or BT paring, control 506 forinitiating or pausing playback of content, control 504 for fastreversing playback or skipping backward one track, and control 508 forfast forwarding playback or skipping forward one track. Some are all ofthe control elements 504-512 may serve multiple rolls based on changingscenarios. For example, for playback of video content or for informationdisplayed on display 180 (e.g., a touch screen), controls 503 and 507may be used to increase “+” and decrease “−” brightness of display 180.Control 509 may be used to transfer or pick up a phone call or othercontent on a user device 202, for example. Proximity detection islands520 and/or control elements 503-512 may be backlit (e.g., using LED's orthe like) for night or low-light visibility.

Moving on to FIG. 6, a block diagram 600 depicts one example of aproximity detection island 520. Proximity detection island 520 may beimplemented using a variety of technologies and circuit topologies andthe example depicted in FIG. 6 is just one such non-limiting example andthe present application is not limited to the arrangement of elementsdepicted in FIG. 6. One or more proximity detection islands 520 may bepositioned on, connected with, carried by or otherwise mounted on mediadevice 100. For example, proximity detection island 520 may be mountedon a top surface 199 t of chassis 199. A structure 650 made from anoptically transmissive material such as glass, plastic, a film, anoptically transparent or translucent material, or the like. Structure650 may be made from a material that allows light 603, 607, 617, and 630to pass through it in both directions, that is, bi-directionally.Structure 650 may include apertures 652 defined by regions 651 (e.g., anopaque or optically reflective/absorptive material) used for providingoptical access (e.g., via apertures 652) to an environment ENV 198external to the media device 100 for components of the proximitydetection island 520. Structure 650 may be configured to mount flushwith top surface 199 t, for example. In some examples, structure 650 maynot include regions 651.

Proximity detection island 520 may include at least one LED 601 (e.g.,an infrared LED—IR LED) electrically coupled with driver circuitry 610and configured to emit IR radiation 603, at least one IR opticaldetector 605 (e.g., a PIN diode) electrically coupled with ananalog-to-digital converter ADC 612 and configured to generate a signalin response to IR radiation 607 incident on detector 605, and at leastone indicator light 616 electrically coupled with driver circuitry 614and configured to generate colored light 617. As depicted, indicatorlight 616 comprises a RGB LED configured to emit light 617 in a gambitof colors indicative of status as will be described below. Here, RGB LED616 may include four terminals, one of which coupled with circuitground, a red “R” terminal, a green “G” terminal, and a blue “B”terminal, all of which are electrically connected with appropriatecircuitry in driver 614 and with die within RGB LED 616 to effectuategeneration of various colors of light in response to signals from driver614. For example, RGB LED 616 may include semiconductor die for LED'sthat generate red, green, and blue light that are electrically coupledwith ground and the R, G, and B terminals, respectively. One skilled inthe art will appreciate that element 616 may be replaced by discreteLED's (e.g., separate red, green, white, and blue LED's) or a singlenon-RGB LED or other light emitting device may be used for 616. Thevarious colors may be associated with different users who approach andare detected in proximity of the media device and/or different userdevices that are detected by the media device. Therefore, if there arefour users/and our user devices detected, then: the color blue may beassociated with user #1; yellow with user #2; green with user #3; andred with user #4. Some users and or user devices may be indicated usingalternating colors of light such as switching/flashing between red andgreen, blue and yellow, blue and green, etc. In other examples othertypes of LED's may be combined with RGB LED 616, such as a white LED,for example, to increase the number of color combinations possible.

Optionally, proximity detection island 520 may include at least onelight sensor for sensing ambient light conditions in the ENV 198, suchas ambient light sensor ALS 618. ALS 618 may be electrically coupledwith circuitry CKT 620 configured to process signals from ALS 618, suchas optical sensor 609 (e.g., a PIN diode) in response to ambient light630 incident on optical sensor 609. Signals from CKT 620 may be furtherprocessed by ADC 622. The various drivers, circuitry, and ADC's ofproximity detection island 520 may be electrically coupled with acontroller (e.g., a μC, a μP, an ASIC, or controller 101 of FIG. 1) thatis electrically coupled with a bus 645 (e.g., bus 110 of FIG. 1) thatcommunicates signals between proximity detection island 520 and othersystems of media device 100. Proximity detection island 520 may includeauditory system AUD 624 configured to generate sound or producevibrations in response to presence detection or other signals. AUD 624may be mechanically coupled 641 with chassis 199 to cause chassis 199 tovibrate or make sound in response to presence detection or othersignals. In some examples AUD 624 may use SPK 160 to generate sound orvibration. In other examples AUD 624 may use a vibration motor, such asthe type used in smartphones to cause vibration when a phone call ornotification is received. In yet another example, AUD 624 may use apiezoelectric film that deforms in response to an AC or DC signalapplied to the film, the deformation generating sound and/or vibration.In yet other examples, AUD 624 may be connected with or mechanicallycoupled with one or more of the control elements and/or one or more ofthe proximity detection islands 520 depicted in FIG. 5 to provide hapticand/or tactile feedback. Upon detecting and acknowledging an approach bya user and/or user device, media may generate sound (e.g., from SPK 160)in a rich variety of tones and volume levels to convey informationand/or media device status to the user. For example, a tone and volumelevel may be used to indicate the power status of the media device 100,such as available charge in BAT 135 of power system 111. The volume ofthe tone may be louder when BAT 135 is fully charged and lower forreduced levels of charge in BAT 135. Other tones and volume levels maybe used to indicate the media device 100 is ready to receive input fromthe user or user device, the media device 100 is in wirelesscommunications with a WiFi router or network, cellular service,broadband service, ad hoc WiFi network, other BT enabled devices, forexample.

Proximity detection island 520 may be configured to detect presence of auser 201 (or other person) that enters 671 an environment 198 the mediadevice 100 is positioned in. Here, entry 671 by user 201 may include ahand 601 h or other portion of the user 201 body passing within opticaldetection range of proximity detection island 520, such as hand 601 hpassing over 672 the proximity detection island 520, for example. IRradiation 603 from IRLED 603 exiting through portal 652 reflects offhand 601 h and the reflected IR radiation 607 enters portal 652 and isincident on IR detector 605 causing a signal to be generated by ADC 612,the signal being indicative of presence being detected. RGB LED 616 maybe used to generate one or more colors of light that indicate to user201 that the user's presence has been detected and the media device isready to take some action based on that detection. The action taken willbe application specific and may depend on actions the user 201programmed into CFG 125 using APP 225, for example. The action takenand/or the colors emitted by RGB LED 616 may depend on the presenceand/or detection of a user device 210 in conjunction with or instead ofdetection of presence of user 201 (e.g., RF 565 from device 210 by RF107).

As described above, proximity detection island 520 may optionallyinclude ambient light sensor ALS 618 configured to detect ambient light630 present in ENV 198 such as a variety of ambient light sourcesincluding but not limited to natural light sources such as sunny ambient631, partially cloudy ambient 633, inclement weather ambient 634, cloudyambient 635, and night ambient 636, and artificial light ambient 632(e.g., electronic light sources). ALS 618 may work in conjunction withIRLED 610 and/or IR detector 605 to compensate for or reduce errors inpresence detection that are impacted by ambient light 630, such as IRbackground noise caused by IR radiation from 632 or 631, for example. IRbackground noise may reduce a signal-to-noise ratio of IR detector 605and cause false presence detection signals to be generated by ADC 612.

ALS 618 may be used to detect low ambient light 630 condition such asmoonlight from 636 or a darkened room (e.g., light 632 is off), andgenerate a signal consistent with the low ambient light 630 conditionthat is used to control operation of proximity detection island 520and/or other systems in media device 100. As one example, if userapproaches 671 proximity detection island 520 in low light or no lightconditions as signaled by ALS 618, RGB LED 616 may emit light 617 at areduced intensity to prevent the user 201 from being startled or blindedby the light 617. Further, under low light or no light conditions AUD624 may be reduced in volume or vibration magnitude or may be muted.Additionally, audible notifications (e.g., speech or music from SPK 160)from media device 100 may be reduced in volume or muted under low lightor no light conditions (see FIG. 9).

Structure 650 may be electrically coupled 681 with capacitive touchcircuitry 680 such that structure 650 is operative as a capacitive touchswitch that generates a signal when a user (e.g., hand 601 h) touches aportion of structure 650. Capacitive touch circuitry 680 may communicate682 a signal to other systems in media device 100 (e.g., I/O 105) thatprocess the signal to determine that the structure 650 has been touchedand initiate an action based on the signal. A user's touch of structure650 may trigger driver 614 to activate RGB LED 616 to emit light 617 toacknowledge the touch has been received and processed by media device100.

Reference is now made to FIG. 7, where top plan views of differentexamples of proximity detection island 520 configurations are depicted.Although the various example configurations and shapes are depicted aspositioned on top surface 199 t of chassis 199, the present applicationis not so limited and proximity detection islands 520 may be positionedon other surfaces/portions of media device 100 and may have shapesdifferent than that depicted. Furthermore, media device 100 may includemore or fewer proximity detection islands 520 than depicted in FIG. 7and the proximity detection islands 520 need not be symmetricallypositioned relative to one another. Actual shapes of the proximitydetection islands 520 may be application specific and may be based onesthetic considerations. Configuration 702 depicts five rectangularshaped proximity detection islands 520 positioned on top surface 199 twith four positioned proximate to four corners of the top surface 199 tand one proximately centered on top surface 199 t. Configuration 704depicts three circle shaped proximity detection islands 520 proximatelypositioned at the left, right, and center of top surface 199 t.Configuration 706 depicts four hexagon shaped proximity detectionislands 520 proximately positioned at the left, right, and two at thecenter of top surface 199 t. Finally, configuration 708 depicts twotriangle shaped proximity detection islands 520 proximately positionedat the left, right of top surface 199 t. In some examples there may be asingle proximity detection island 520. Proximity detection islands 520may be configured to operate independently of one another, or incooperation with one another.

Moving to FIG. 8A, a top plan view of proximity detection island 520coverage is depicted. Each proximity detection island 520 may bedesigned to have a coverage pattern configured to detect presence ofuser 201 when the user 201 or portion of the user body (e.g., hand 801h) enters the coverage pattern. Here, the coverage pattern may besemicircular 810 or circular 830, for example. Semicircular 810 coveragepattern may extend outward a distance R1 (e.g., approximately 1.5meters) from proximity detection island 520 and may span a distance D1about a center 871 of proximity detection island 520. Semicircular 810coverage patterns of the four proximity detection islands 520 may notoverlap one another such that there may be a coverage gap X1 and Y1between the adjacent coverage patterns 810. Entry 825 of hand 801 h orentry 820 of user 201 may cause one or more of the proximity detectionislands 520 to indicate 840 that a presence has been detected, byemitting a color of light from RGB LED 616, for example. In otherexamples, the coverage pattern may be circular 830 and cover a 360degree radius 870 about a center point 871 of proximity detection island520. Circular 830 coverage pattern 830 may or may not overlap thecircular 830 pattern of the other proximity detection islands 520.

FIG. 8C depicts a front view 800 b of media device 100 and a coveragepattern 860 that has an angular profile Ω about center point 871. Hand801 h entering 825 into the coverage pattern 860 is detected byproximity detection island 520 and detection of hand 810 triggers light840 being generate by RGB LED 616 of proximity detection island 520.Detection of hand 810 may also cause information “Info” to be displayedon DISP 180 and/or sound 845 to be generated by SPK 160. In FIG. 8C, aside view 800 c of media device 100 is depicted with proximity detectionisland 520 having angular profile a about center point 871 for acoverage pattern 880. Hand 801 h entering 825 into the coverage pattern880 is detected by proximity detection island 520 and detection of hand810 triggers light 840 being generate by RGB LED 616 of proximitydetection island 520 and AUD 624 generating vibration 847.

Attention is now directed to FIG. 9, where a top plan view 900 of mediadevice 100 depicts four proximity detection islands 520 denoted as I1,I2, I3, and I4. Furthermore, control elements 503-512 are depicted ontop surface 199 t. In the example depicted, hand 901 h enters intoproximity detection range of at least proximity detection island I1 andtriggers generation of light (917 a-d) from one or more of the islands(I1, I2, I3, I4) such as light 617 from RGB LED 616 of FIG. 6, forexample. Presence detection by proximity detection island I1 may cause avariety of response from media device 100 including but not limited tosignaling that presence has been detected using light (917 a-d),generating sound 845 from SPK 160, vibration 847, displaying info 840 onDISP 180, capturing and acting on content C from user device 220,establishing wireless communications 126 with user device 220 or otherwireless device (e.g., a wireless router), just to name a few. Presencedetection by proximity detection island I1 may cause media device 100 tonotify user 901 that his/her presence has been detected and the mediadevice is ready to receive input or some other action from user 901.Input and/or action from user 901 may comprise user 901 actuating one ofthe control elements 503-512, touching or selecting an icon displayed onDISP 180, issuing a verbal command or speech detected by MIC 170.

As one example, upon detecting presence of user 901, media device 100may emit light 917 c from proximity detection island I3. If the userdevice 220 is present and also detected by media device 100 (e.g., viaRF signals 126 and/or 563), then the media device 100 may indicate thatpresence of the user device 220 is detected and may take one or moreactions based on detecting presence of the user device 220. If userdevice 220 is one that is recognized by media device 100, then light 917c from proximity detection island I3 may be emitted with a specificcolor assigned to the user device 220, such as green for example.Recognition of user device 220 may occur due to the user device 220having been previously BT paired with media device 100, user device 220having a wireless identifier such as a MAC address or SSID stored in orpre-registered in media device 100 or in a wireless network (e.g., awireless router) the media device 100 and user device 220 are inwireless communications with, for example. DISP 180 may display info 840consistent with recognition of user device 220 and may display via a GUIor the like, icons or menu selections for the user 201 to choose from,such as an icon to offer the user 201 a choice to transfer content Cfrom user device 220 to the media device 100, to switch from BT wirelesscommunication to WiFi wireless communication, for example. As oneexample, if content C comprises a telephone conversation, the mediadevice 100 through instructions or the like in CFG 125 may automaticallytransfer the phone conversation from user device 220 to the media device100 such that MIC 170 and SPK 160 are enabled so that media device 100serves as a speaker phone or conference call phone and media device 100handles the content C of the phone call. If the transfer of content C isnot automatic, CFG 125 or other programming of media device 100 mayoperate to offer the user 201 the option of transferring the content Cby displaying the offer on DISP 180 or via one of the control elements503-512. For example, control element 509 may blink (e.g., viabacklight) to indicate to user 201 that actuating control element 509will cause content C to be transferred from user device 220 to mediadevice 100.

In some examples, control elements 503-512 may correspond to menuselections displayed on DISP 180 and/or a display on the user device220. For example, control elements 512 may correspond to six icons onDISP 180 (see 512′ in FIG. 8) and user 201 may actuate one of thecontrol elements 512 to initiate whatever action is associated with thecorresponding icon on DISP 180, such as selecting a playlist for mediato be played back on media device 100. Or the user 201 may select one ofthe icons 512′ on DISP 180 to effectuate the action.

As one example, if content C comprises an alarm, task, or calendar eventthe user 201 has set in the user device 220, that content C may beautomatically transferred or transferred by user action using DISP 180or control elements 503-512, to media device 100. Therefore, a wake upalarm set on user device 220 may actually be implemented on the mediadevice 100 after the transfer, even if the user device 220 is powereddown at the time the alarm is set to go off. When the user device ispowered up, any alarm, task, or calendar event that has not beenprocessed by the media device 100 may be transferred back to the userdevice 220 or updated on the user device so that still pending alarm,task, or calendar events may be processed by the user device when it isnot in proximity of the media device 100 (e.g., when user 201 leaves fora business trip). CFG 125 and APP 225 as described above may be used toimplement and control content C handling between media device 100 anduser devices.

Some or all of the control elements 503-512 may be implemented ascapacitive touch switches. Furthermore, some or all of the controlelements 503-512 may be backlit (e.g., using LED's, light pipes, etc.).For example, control elements 512 may be implemented as capacitive touchswitches and they may optionally be backlit. In some examples, afterpresence is detected by one or more of the proximity detection islands(I1, I2, I3, I4), one or more of the control elements 503-512 may bebacklit or have its back light blink or otherwise indicate to user 201that some action is to be taken by the user 201, such as actuating(e.g., touching) one or more of the backlit and/or blinking controlelements 512. In some examples, proximity detection islands (I1, I2, I3,I4) may be configured to serve as capacitive touch switches or anothertype of switch, such that pressing, touching, or otherwise actuating oneor more of the proximity detection islands (I1, I2, I3, I4) results insome action being taken by media device 100.

In FIG. 9, actions taken by media device 100 subsequent to detectingpresence via proximity detection islands (I1, I2, I3, I4) and/or othersystems such as RF 107, SEN 195, MIC 170, may be determined in part onambient light conditions as sensed by ALS 618 in proximity detectionislands (I1, I2, I3, I4). As one example, if ambient light 630 is bright(e.g., 631 or 632), then brightness of DISP 180 may be increased, light917 a-d from islands may be increased, and volume from SPK 160 may benominal or increased because the ambient light 630 conditions areconsistent with waking hours were light intensity and volume may not bea distraction to user 201. On the other hand, if ambient light 630 isdim or dark (e.g., 636), then brightness of DISP 180 may be decreased,light 917 a-d from islands may be decreased, and volume from SPK 160 maybe reduced or muted because the ambient light 630 conditions areconsistent with non-waking hours were light intensity and volume may bea distraction to or startle user 201. Other media device 100 functionssuch as volume level, for example, may be determined based on ambientlight 630 conditions (e.g., as detected by ALS 618 of island I4). As oneexample, under bright ambient light 630 conditions, volume VH of SPK 160may be higher (e.g., more bars); whereas, under low ambient light 630conditions, volume VL of SPK 160 may be lower (e.g., fewer bars) or maybe muted entirely VM. Conditions other than ambient light 630 may causemedia device 100 to control volume as depicted in FIG. 9.

FIG. 10 depicts one example of a flow 1000 for presence detection,notification, and media device readiness. At a stage 1002 a query as towhether or not an approach is detected by one or more of the proximitydetection islands (e.g., I1, I2, I3, I4) is made. Here, the query may beby controller CNTL 640 or controller 101, for example. If one or more ofthe proximity detection islands have detected presence, then a YESbranch is taken. If no presence is detected by one or more of theproximity detection islands, then a NO branch is taken and the flow 1000may return to the stage 1002 to wait for one or more of the proximitydetection islands to detect a presence. The YES branch takes flow 1000to a stage 1004 where a notification is executed by the media device 100using light, sound, or vibration to notify a user that presence has beendetected, for example, using one or more colors of light (e.g., from RGBLED's 616) and/or an auditory cue (e.g., from SPK 160, vibration from847, or from a passive radiator used as one of the SPK 160). At as stage1006, the media device 100 indicates that it is ready to receive inputfrom a user and/or user device (e.g., user 201 or a user device 220 viaRF 107). At a stage 1008 a query is made as to whether or not an inputis received from a user. If an input is received from the user and/oruser device, then a YES branch is taken to a stage 1010 where the mediadevice 100 takes an appropriate action based on the type of user inputreceived and the flow may terminate after the stage 1010. Appropriateactions taken by media device 100 will be application dependent and maybe determined in whole or in part by APP 225, CFG 125, executableprogram code, hardware, etc. Inputs from the user includes but is notlimited to actuation of one or more of the control elements 503-512,touching an icon or other area of DISP 180, issuing a spoken command orspeech detected by MIC 170, taking an action on user device 220 that iswirelessly communicated to media device 100, just to name a few. If noinput is received from the user and/or user device, then a NO branch istaken and the flow 1000 may continue at a stage 1012 where flow 1000 mayenter into a wait period of predetermined time (e.g., of approximately15 seconds or one minute, etc.). If a user input is received before thewait period is over, then a NO branch may be taken to the stage 1010. Ifthe wait period is over, then a YES branch may be taken and flow 1000may resume at the stage 1002.

FIG. 11 depicts another example of a flow 1100 for presence detection,notification, and media device readiness. At a stage 1102 a query as towhether an approach is detected by one or more of the proximitydetection islands (e.g., I1, I2, I3, I4) is made. If one or more of theproximity detection islands have detected presence, then a YES branch istaken. If no presence is detected by one or more of the proximitydetection islands, then a NO branch is taken and the flow 1100 mayreturn to the stage 1102 to wait for one or more of the proximitydetection islands to detect a presence. The YES branch takes flow 1100to a stage 1104 where a query is made as to whether or not ambient light(e.g., ambient light 630 as detected by ALS 618 of FIG. 6) is a factorto be taken into consideration in the media devices response to havingdetected a presence at the stage 1102. If ambient light is not a factor,then a NO branch is taken and the flow 1100 continues to a stage 1106.If ambient light is a factor, then a YES branch is taken and flow 1100continues at a stage 1108 where any notification by media device 100 inresponse to detecting presence at the stage 1102 is modified. One ormore of light, sound, or vibration may be used by media device 100 toindicate to a user that its presence has been detected. The light,sound, or vibration are altered to comport with the ambient lightconditions, such as described above in regard to ambient light 630 inFIG. 9, for example. At the stage 1106, notification of presence beingdetected occurs using one or more of light, sound, or vibration withoutmodification. At a stage 1110, the media device 100 indicates that it isready to receive input from a user and/or user device (e.g., user 201 ora user device 220 via RF 107). At a stage 1112 a query is made as towhether or not an input is received from a user. If an input is receivedfrom the user and/or user device, then a YES branch is taken to a stage1114 where the media device 100 takes an appropriate action based on thetype of user input received and the flow may terminate after the stage1114. If no input is received from the user and/or user device, then aNO branch is taken and the flow 1110 may continue at a stage 1116 whereflow 1100 may enter into a wait period of predetermined time (e.g., ofapproximately 15 seconds or one minute, etc.). If a user input isreceived before the wait period is over, then a NO branch may be takento the stage 1114. If the wait period is over, then a YES branch may betaken and flow 1100 may resume at the stage 1102. Actions taken at thestage 1114 may include those described above in reference to FIG. 10.

FIG. 12 depicts yet another example of a flow 1200 for presencedetection, notification, and media device readiness. At a stage 1202 aquery as to whether an approach is detected by one or more of theproximity detection islands (e.g., I1, I2, I3, I4) is made. If one ormore of the proximity detection islands have detected presence, then aYES branch is taken. If no presence is detected by one or more of theproximity detection islands, then a NO branch is taken and the flow 1200may return to the stage 1202 to wait for one or more of the proximitydetection islands to detect a presence. The YES branch takes flow 1200to a stage 1204 where a query is made as to whether or not detection ofRF (e.g., by RF 107 using antenna 124) is a factor to be taken intoconsideration in the media devices response to having detected apresence at the stage 1202. If RF detection is not a factor, then a NObranch is taken and the flow 1200 continues to a stage 1206. If RFdetection is a factor, then a YES branch is taken and flow 1200continues at a stage 1208 where any notification by media device 100 inresponse to detecting presence at the stage 1202 is modified. One ormore of light, sound, or vibration may be used by media device 100 toindicate to a user that its presence has been detected. The light,sound, or vibration are altered to comport with the detection of RF(e.g., from a user device 220), such as described above in regards touser device 220 in FIG. 9, for example. At the stage 1206, notificationof presence being detected occurs using one or more of light, sound, orvibration without modification. At a stage 1210, the media device 100indicates that it is ready to receive input from a user and/or userdevice (e.g., user 201 or a user device 220 via RF 107). At a stage 1212a query is made as to whether or not an input is received from a user.If an input is received from the user and/or user device, then a YESbranch is taken to a stage 1214 where the media device 100 takes anappropriate action based on the type of user input received and the flowmay terminate after the stage 1214. If no input is received from theuser and/or user device, then a NO branch is taken and the flow 1200 maycontinue at a stage 1216 where flow 1200 may enter into a wait period ofpredetermined time (e.g., of approximately 15 seconds or one minute,etc.). If a user input is received before the wait period is over, thena NO branch may be taken to the stage 1214. If the wait period is over,then a YES branch may be taken and flow 1200 may resume at the stage1202. Actions taken at the stage 1214 may include those described abovein reference to FIGS. 9 and 10.

FIG. 13 depicts one example 1300 of presence detection using proximitydetection islands and/or other systems responsive to wireless detectionof different users (e.g., hands 1300 a-d) and/or different user devices(e.g., 220 a-220 d). In FIG. 13 four users denoted by hands 1300 a-d andtheir respective user devices 220 a-220 b enter 925 proximity detectionrange of one or more of the proximity detection islands (I1, I2, I3,I4). Although four users and four user devices are depicted, there maybe more or fewer than depicted in FIG. 13. Detection of user devices 220a-220 b may be through wireless means such as RF 107 (e.g., via antenna124/129) and its various transceivers wirelessly communicating 126 orwirelessly detecting RF 563 from those user devices. For example,considering just one of the users and one of the user devices, hand 1300b enters 925 detection range of proximity detection island I2 and isdetected 597 by island I2. Island I2 notifies user via light 1317 b thathis/her presence has been detected. User device 220 b may be carried bythe user at the same time or at approximately the same time as theuser's presence is detected by island I2. Therefore, RF 107 may detectRF 563, may attempt to wirelessly connect 126, or be in wireless 126communications with user device 220 b. Accordingly, notifications andactions described above in regards to flow 1200 of FIG. 12 may occur inmedia device 100 in response to detecting presence 597 at or near thesame time as detecting RF from a user device. Media device 100 may emitsound 1345, vibrate 847, display information info on DISP 180, generatelight 1317 a-1317 d, await actuation of one or more of the controlelements 503-512, or other action(s), for example. At the same time orat different times, other users denoted by hands 1300 a, 1300 c, and1300 d may be detected 597 by one or more of the proximity detectionislands (I1, I2, I3, I4) along with RF 563 from user devices 220 a, 220c, and 220 d being detected by RF 107. Media device 100 may takeappropriate action(s) and make appropriate notification(s) as describedherein in response to proximity detection and RF detection occurring inclose time proximity to one another, simultaneously, nearlysimultaneously, or in some sequence. In that a range for RFtransmissions may typically be greater than a detection range for theproximity detection islands (I1, I2, I3, I4), in some examples the RFsignatures or signals of user device 220 a-d may be detected by RF 107before the proximity detection islands (I1, I2, I3, I4) detect presenceof the users 1300 a-d. For example, RF 107 may detect RF 563 before theuser device emitting RF 563 is approximately 10 meters or more away frommedia device 100 (e.g., for BT transmissions) or much more than 10meters away for other wireless technologies (e.g., for WiFitransmissions). Therefore, in some examples, RF 107 will detect RFsignals prior to proximity detection islands (I1, I2, I3, I4) detectingpresence 597.

Users devices 220 a-220 d may be pre-registered or otherwise associatedor known by media device 100 (e.g., via CFG 125 or other) and theactions taken and notifications given by the media device 100 maydepended on and may be different for each of the user devices 220 a-220d. For example, after detection and notification based on detectingproximity 597 and RF 563 for user device 220 a, media device 100 mayestablish or re-establish BT pairing (e.g., via BT 120 in RF 107) with220 a and content C on 220 a (e.g., a phone conversation) may betransferred to media device 100 for handling via SPK 160 and MIC 170.CFG 125 and/or APP 225 on 220 a may affect how media device and userdevice 220 a operate post detection.

As another example, post detection 597 & 563 and notification for userdevice 220 d may result in content C (e.g., music from MP3 files) on 220d being played back 1345 on media device 100. Control elements 503-512may be activated (if not already activated) to play/pause (506), fastforward (508), fast reverse (504), increase volume (503), decreasevolume (507), or mute volume (509). Control elements 512 may be used toselect among various play lists or other media on user device 220 d.

In another example, content C on user device 220 c may, post detectionand notification, be displayed on DISP 180. For example, a web page thatwas currently being browsed on 220 c may be transferred to media device100 for viewing and browsing, and a data payload associated with thebrowsing may also be transferred to media device 100. If content Ccomprises a video, the display and playback functions of the video maybe transferred to media device 100 for playback and control, as well asthe data payload for the video.

Content C this is transferred to media device 100 may be transferredback in part or whole to the user devices depicted, when the user is nolonger detectable via islands to proximity detection islands (I1, I2,I3, I4) or other systems of media device 100, by user command, or byuser actuating one of the control elements 503-512 or an icon or thelike on DISP 180, for example.

FIG. 14 depicts one example 1400 of proximity detection islandsassociated with specific device functions. Examples of functions thatmay be assigned to or fixed to a proximity detection island (I1, I2, I3,I4) include but are not limited to “Set Up” of media device 100, “BTParing” between media device 100 and one or more BT equipped devices,“Shut-Off” of media device 100 (e.g., power off or placing media device100 in a standby mode, a low power consumption mode, or a sleep mode),and “Content” being handled by media device 100, such as the last mediafiled that was played on, the last buffered channel, the last playlistthat was being accessed by, or the last Internet site or stream beinghandled by media device 100. One or more of proximity detection islands(I1, I2, I3, I4) may serve as indicators for the functions associatedwith them or may serve to actuate those functions by pressing ortouching a surface of the island (e.g., as a switch or capacitive touchswitch or button, see FIG. 6). For example, a finger of hand 1400 h maytouch structure 650 of island I2 to activate the “BT Pairing” betweenthe media device 100 and user device 220, the touch activating thecapacitive touch function of island I2 (e.g., causing island I2 to serveas a switch). Island I2 may emit light 1417 b to acknowledge the touchby hand 1400 h. CFG 125 and/or APP 225 may be used to assign andre-assign functions to one or more of the proximity detection islands(I1, I2, I3, I4) and the functions assigned and the proximity islandsthey are assigned to may be user dependent and/or user device dependent.As another example, pressing or touching island I4 may turn power off tothe media device 100, or may place media device 100 in a low power,standby, or sleep mode.

In other examples, one or more of the control elements 503-512 or anicon or the like on DISP 180 may be actuated or selected by a user inconnection with one of the functions assigned to proximity detectionislands (I1, I2, I3, I4). For example, to activate the “BT Pairing”function of island I2, control element 512 that is nearest 1427 toisland I2 may be actuated by the user. In another example, proximitydetection islands (I1, I2, I3, I4) may be associated with differentusers whose presence has been detected by one or more of the islands.For example, if proximity of four users (U1, U2, U3, U4) has beendetected by any of the islands, then U1 may be associated with I4, U2with I1, U3 with I2, and U4 with I3. Association with an island may beused to provide notifications to the user, such as using light from RGBLED 616 to notify the user of status (e.g., BT pairing status) or otherinformation.

FIG. 15 depicts one example 1500 of content handling from a user devicesubsequent to proximity detection by islands 520 and/or wireless systemsof media device 100. User 1500 h is detected 1540 by proximity detectionisland 520 which emits light 1517, sound 1545, vibration 847, anddisplay of information info on DISP 180 to indicate that media device100 has detected presence and is ready to receive user input. Userdevice 220 may also have been detected by a transceiver RXTX 1507 in RF107. RXTX 1507 may represent any transceiver in RF 107 such as BT 120,WiFi 130, AH 140, or other 150. Media device 100, post detection, may bewirelessly connected with user device 220 using a variety of wirelesspaths such as a direct wireless connection 126 between media device 100and user device 220, and wireless connections 1565 and 1563 via wirelessrouter 1570, for example. Content C on user device 220 may be handled orotherwise stored or routed to media device from the user device 220 orfrom Cloud 1550 using a variety of wireless paths. Cloud 1550 mayrepresent the Internet, an intranet, a server farm, a download site, amusic store, and application store, Cloud storage, a web site, just toname a few. Information including but not limited to content C, data D,a playlist PL, a stream or streaming service S, and a URL, just to namea few. Although content C is depicted as being presently on user device220, one or more of the information in Cloud 1550 may also be presentlyon user device or wirelessly accessible to user device 220 via wirelessconnections 1561, 1563, 1567, 126, 1569, and 1565. Some of the wirelessconnections may be made through wireless router 1570 or media device 100(e.g., via WiFi 130).

In some examples, content C or other information resident or accessibleto user device 220 may be handled by media device 100. For example, if Ccomprises media files such as MP3 files, those files may be wirelesslyaccessed by media device 100 by copying the files to DS 103 (e.g., inFlash memory 145) thereby taking the data payload and wireless bandwidthfrom the user device 220 to the media device 100. Media device 100 mayuse it wireless systems to access 1569 or 1565 and 1567 the informationfrom Cloud 1550 and either store the information locally in DA 103 orwirelessly access the information as it is played back or otherwiseconsumed or used by media device 100. APP 225 and CFG 125 may includeinformation and executable instructions that orchestrate the handling ofcontent between media device 100, user device 220, and Cloud 1550. Forexample, a playlist PL on user device 220 may be located in Cloud 1550and media files associated with music/videos in the PL may be found atURL in Cloud 1550. Media device 100 may access the media files from thelocation specified by the URL and wirelessly stream the media files, ormedia device may copy a portion of those media files to DS 103 and thenplayback those files from its own memory (e.g., Flash 145).

In other examples, user 1500 h may be one of many users who have contentto be accessed and/or handled by media device 100. Post detection,songs, play lists, content, of other information on user device 220 orfrom Cloud 1550 may be placed in a queue with other information ofsimilar type. The queue for songs may comprise Song 1 through Song N andsongs on user device 220 that were active at the time of proximitydetection may be placed in some order within the queue, such as Song 4for being fourth in line in queue for playback on media device 100.Other information such as play lists PL 1-PL N or other content such asC 1-C N may be placed in a queue for subsequent action to be taken onthe information once it has moved to the top of the queue. In someexamples, the information on user device 220 or from Cloud 1550 may bebuffered in media device 100 by storing buffered data in DS 103.

FIG. 16 depicts another example of content handling from user devicessubsequent to proximity detection. In FIG. 16, a plurality of users 1601a-1601 n and their associated user device 220 are detected by mediadevice 100 are queued into DS 103 on media device 100 for handling orare buffered BUFF into DS 103 in some order. Detection of each user andor user device may be indicated with one or more different colors oflight 1517, different sounds 1545, different vibration 847 patterns, ordifferent info on DISP 180. In some examples, buffering BUFF occurs instorage 1635 provided in Cloud 1550. In FIG. 16, users 1601 a-1601 nhave information on their respective user devices 220 that may behandled by media device 100 such as Song 1-Song N, PL 1-PL N, C 1-C N.The information from the plurality of users 1601 a-1601 n is queueand/or buffered BUFF on media device 100 and/or in Cloud 1550, that is,media device may handle all of the information internally, in Cloud1550, or some combination of media device 100 and Cloud 1550. Forexample, if a data storage capacity of the information exceeds a storagecapacity of DS 103, then some or all of the data storage may be offloaded to Cloud 1550 (e.g., using Cloud storage or a server farm).Information from users 1601 a-1601 n may be played back or otherwisehandled by media device 100 in the order in which proximity of the userwas detected or in some other order such as a random order or a shuffleplay order. For example, DISP 180 may have an icon RDM which may beselected for random playback.

FIG. 17 depicts one example of content handling from a data capablewristband or wristwatch subsequent to proximity detection by a mediadevice. A hand 1700 h of a user may comprise a user device in the formof a data capable wristband or wristwatch denoted as 1740. Wristband1740 may include information “I” that is stored in the wristband 1740and is wirelessly accessible using a variety of wireless connectionsbetween media device 100, wireless router 1570, and Cloud 1750. Mediadevice 100 may serve as a wireless hub for wristband 1740 allowingwristband 1740 to send and retrieve information from Cloud 1750 viawireless connections between media device 100 and wireless router 1570and/or Cloud 1750. For example, wristband 1740 may use BT to wirelesslycommunicate with media device 100 and media device 100 uses its WiFi 130to wirelessly communicate with other resources such as Cloud 1750 androuter 1570. Detection 1540 of hand 1700 h and/or device 1740 maytrigger the emission of light 1517, generation of sound 1545, vibration847, and display of information info on DISP 180.

Information “I” included in wristband 1740 may include but is notlimited to alarms A, notifications N, content C, data D, and a URL. Upondetection of proximity, any of the information “I” may be wirelesslycommunicated from wristband 1740 to media device 100 where theinformation “I” may be queued (A 1-A N; D 1-D N, N1-N n; and C 1-C N)and/or buffered BUFF as described above. In some examples, postdetection, wristband 1740 may wirelessly retrieve and/or store theinformation “I” from the media device 100, the Cloud 1750, or both. Asone example, if wristband 1740 includes one or more alarms A, postdetection those alarms A may be handled by media device 100. Therefore,if one of the alarms A is set to go off at 6:00 pm and detection occursat 5:50 pm, then that alarm may be handled by media device 100 using oneor more of DISP 180, SPK 160, and vibration 847, for example. If anotheralarm is set for 5:30 am and the wristband 1740 and media device 100 arestill in proximity of each another at 5:30 am, then the media device 100may handle the 5:30 am alarm as well. The 6:00 pm and 5:30 am alarms maybe queued in the alarms list as one of A 1-AN. When wristband 1740 andmedia device 100 are no longer in proximity of each other, any alarmsnot processed by media device 100 may be processed by wristband 1740.

In FIG. 18, a plurality of users 1801 a-1801 n and their respectivewristwatches 1740 are detected by one or more proximity detectionislands 520 of media device 100 and/or or other systems such as RF 107.Detection of each user and or device 1740 may be indicated with one ormore different colors of light 1517, different sounds 1545, differentvibration 847 patterns, or different info on DISP 180. Here, eachwristwatch 1740 includes information “I” specific to its user and aseach of these users and wristwatches come into proximity and aredetected, information “I” may be queued, buffered BUFF, or otherwisestored or handled by media device 100 or in Cloud 1750. For example,data D may include exercise, nutrition, dietary data, and biometricinformation collected from or sensed via sensors carried by thewristwatch 1740. Data D may be transferred to media device 100 or Cloud1750 and accessed via a URL to a web page of a user. The data D may beshared among other users via their web pages. For example, some or allof users 1801 a-1801 n may be consent to sharing their information “I”through media device 100, Cloud 1750, or both. Users 1801 a-1801 n mayview each other's information “I” on DISP 180 or go to a URL in Cloud1750 or the like to view each other's information “I”. Information “I”that is displayer on DISP 180 may be buffered BUFF, queued (A 1-A N; D1-D N, N1-N n; and C 1-C N), or otherwise stored on media device 100(e.g., in DS 103) for each user to query as desired. A non-transitorycomputer readable medium such as CFG 125 and/or APP 225 may be used todetermine actions taken by wristwatch 1740 (e.g., via APP 225) and mediadevice (e.g., via CFG 125).

In FIG. 19, one example of a flow 1900 for content C handling on a mediadevice 100 or other location, post proximity detection includes themedia device 100 accessing the content C at a stage 1902. Here,accessing may include negotiating the necessary permissions, user namesand passwords, or other tasks necessary to gain access to the content Con a user device or located elsewhere (e.g., in the Cloud, on a website,or on the Internet). Accessing the content C may include wirelesslyconnecting with the user device or other source of the content C. At astage 1904 the media device 100 makes a determination is made as to thetype of the content C, such as a media file (e.g., music, video,pictures), a web page (e.g., a URL), a file, a document (e.g., a PDFfile), for example. At a stage 1906 the media device 100 makes adetermination as to a status of the content C. Examples of statusinclude but are not limited to static content C (e.g., a file) anddynamic content C (e.g., a stream or a file currently being accessed orplayed back). At a stage 1908 the media device 100 handles the content Cbased on its type and status from stages 1904 and 1906.

In that there may be many user devices to service post proximitydetection or more than one item of content C to be handled from one ormore user devices, at a stage 1910 media device 100 queries the userdevices to see if there is additional content C to be handled by themedia device 100. If additional content exists, then a YES branch may betaken and flow 1900 may return to stage 1902. If no additional content Cis to be handled, then a NO branch may be taken and at a stage 1912 adecision to terminate previously handled content C may be made. Here, auser device may have handed over content C handling to media device 100post proximity detection, but when the user device moves out of RFand/or proximity detection range (e.g., the user leaves with his/heruser device in tow), then media device 100 may release or otherwisedivorce handling of the content C. If previously handled content C doesnot require termination, then a NO branch may be taken and flow 1900 mayend. On the other hand, if previously handled content C requirestermination, then a YES branch may be taken to a stage 1914 were thepreviously handled content C is released by the media device 100.Release by media device 100 includes but is not limited to wirelesslytransferring the content C back to the user device or other location,deleting the content C from memory in the media device 100 or otherlocation, saving, writing or redirecting the content C to a locationsuch as /dev/null or a waste basket/trash can, halting streaming orplayback of the content C, storing the content C to a temporarylocation, just to name a few.

FIG. 20 depicts one example of a flow 2000 for storing, recording, andqueuing content C on a media device 100 or other location post proximitydetection. After content C has been handled by media device 100 (e.g.,stage 1908 of FIG. 19), media device 100 may determine a size (e.g.,file size) of the content C at a stage 2002. The size determination maybe made in order for the media device 100 to determine if the mediadevice 100 has the memory resources to handle and/or store the contentC. If the media device 100 cannot accommodate content C due to size,then media device 100 may select another source for the content C oraccess the content from the user device or other location where it isstored. At a stage 2004 the media device 100 determines whether or notthe content C is dynamic. Examples of dynamic content C include but arenot limited to content C on a user device that is currently beingaccessed or played back on the user device. The dynamic content C mayreside on the user device or may be accessed from another location(e.g., the Cloud or Internet). If the content C is not dynamic (e.g., isstatic such as file), then a NO branch may be taken to a stage 2010where the media device 100 selects an appropriate location to storecontent C based on its size from the stage 2002. Examples of appropriatelocations include but are not limited to a user device, the Cloud, theInternet, an intranet, network attached storage (NAS), a server, and DS103 of media device 100 (e.g., in Flash memory 145). In some examples,media device 100 may include a memory card slot for a SD card, microSDcard, Memory Stick, SSD, CF card, or the like, or a USB connector thatwill accommodate a USB thumb drive or USB hard drive, and those memorydevices may comprise an appropriate location to store content C. At astage 2012 the content C is stored to the selected location. If thecontent C is dynamic, then a YES branch may be taken to a stage 2006where memory device 100 selects an appropriate location to record thedynamic content C to based on the size of the content C. Appropriatelocations include but are not limited to those described above for thestage 2010. At a stage 2008 the media device 100 records the dynamiccontent to the selected location. The selected location may be a buffersuch as BUFF described above. At a stage 2014 a determination may bemade as to whether or not the recording is complete. If the recording isnot complete, then a NO branch may be taken and flow 2000 may return tothe stage 2008. If the recording is complete, then a YES branch may betaken to a stage 2016 where a decision to queue the content C is made.If the content C is not to be queued, then a NO branch may be taken andthe flow 2000 may end. If the content C is to be queued then a YESbranch may be taken and at a stage 2018 the recorded content C or storedcontent C (e.g., from stage 2012) is queued. Queuing may occur asdescribed above in reference to FIGS. 15-18. Media device 100 maymaintain the queue in memory, but the actual content C need not bestored internally in memory device 100 and may be located at some otherlocation such as the Cloud or a user device, for example.

At the stage 2008, the media device 100 may playback other content C(e.g., an mp3 or mpeg file) while recording the content C to theselected location. For example, if three users (U1-U3) approach mediadevice 100 with their respective user devices, are detected by one ormore of the proximity detection islands (e.g., I1, I2, I3, I4) and/or byRF 107, then post detection, media device 100 may begin to handle thecontent C from the various user devices as described in reference toFIGS. 19 and 20. However, assume for purposes of explanation, that usersU1 and U3 have static content C to be handled by media device 100 anduser U2 has dynamic content C. Furthermore, assume that queuing of thecontent C may not be in the order in which media device 100 detected theuser devices, and that order is U2, U3, U1. Now, per flows 1900 and2000, media device 100 begins to record and store the dynamic content Cfrom U2 (e.g., U2 was streaming video); however, the recording is notcomplete and media device 100 handles the content C from U1 next,followed by the content C of U3. Content C from U1 comprises a playlistfor songs stored in the Cloud and C from U3 comprises alarms A,notifications N, and data D from a data capable wristband/wristwatch.Media device 100 handles and stores the content C from U3 in itsinternal memory (e.g., DS 103) and queues U3 content first for display,playback, or other on media device 100. Media device 100 accesses thesongs from U1's playlist from the Cloud and queues U1 next in the queuebehind U3 for playback on the SPK 160 of media device 100. Finally, therecording is complete on U2's dynamic content C and the video stream isrecorded on NAS and media device 100 has accesses to the NAS via WiFi130. U2 is queued behind U1 for playback using DISP 180 and SPK 160 ofmedia device 100. In some examples, where there are not conflicts inhandling content C, the media device may display U3's content C on DISP180 while playing back U1's mp3 songs over SPK 160, even thou U1 isbehind U3 in the queue. Here, there is no or minimal conflict inhandling content C because U1's content is primarily played back usingthe media device's 100 audio systems (e.g., SPK 160) and U3's content Cis primarily visual and is displayed using the media device's 100 videosystems (e.g., DISP 180). Servicing content C from U3 and U1 at the sametime may mean temporarily bumping visual display of U1's playlist onDISP 180 to display U3's content C.

Moving now to FIG. 21 where one example 2100 of a media device 100handling, storing, queuing, and taking action on content from aplurality of user devices is depicted. In FIG. 21, four users denoted byhands 2100 a-d move within proximity detection range of islands 520, aredetected 2140, and the users are notified 2117 of the detection, asdescribed above. The four users 2100 a-d each have their respective userdevices UD1-UD4 having content C1-C4. For purposes of explanation,assume the order in which the user devices are discovered by the mediadevice (e.g., via RF 107) is UD2; UD4; UD3; and UD1 and the content C onthose devices are queued in the same order as the detection as denotedby C2; C4; C3; and C1 in diagram 2180. The media device 100, the userdevices UD1-UD4, wireless router 2170, and Cloud 2150 are all able towirelessly communicate with one another as denoted by 2167.

C2 comprises a playlist and songs, is static, and each song is stored ina mp3 file in memory internal to UD2. As per the flows 1900 and 2000,media device queues C2 first and stores C2 in a SDHC card 2121 such thatthe playlist and mp3 files now reside in SDHC 2121. C1 and C4 bothcomprise information stored in a data capable wristband/wristwatch. C1and C4 are static content. Media device queues C4 behind C2, and storesC4 in Cloud 2150. C3 comprises dynamic content in the form of an audiobook being played back on UD3 at the time it was detected by mediadevice 100. C3 is queued behind C4 and is recorded on NAS 2122 for laterplayback on media device 100. C1 is queued behind C3 and is stored inCloud 2150.

However, the queuing order need not be the order in which content C isplayed back or otherwise acted on by media device 100. In diagram 2180,media device has ordered action to be taken on the queued content in theorder of C1 and C4 first, C2 second and C3 third. C3 may be third inorder because it may still be recording to NAS 2122. The informationcomprising C1 and C4 may be quickly displayed on DISP 180 for itsrespective users to review. Furthermore, the size of data represented byC1 and C4 may be much smaller than that of C2 and C3. Therefore, whileC3 is recording to NAS 2122 and C2 is being copied from UD2 into SDHC2121, action is taken to display C1 and C4 on DISP 180. Action is thentaken on C2 and a portion of the playlist from C2 is displayed on DISP180 with the song currently being played highlighted in that list ofsongs. The music for the song currently being played is output on SPK160. Finally, the recording of C3 is completed and DISP 180 displays thetitle, author, current chapter, and publisher of the audio book. Actionon C3 may be put on hold pending C2 completing playback of the songsstored in SDHC 2121.

Here, media device 100 handled the various types of content C andoperated on one type of content (recording C3) while other content (C1 &C4, C2) were being acted on, such as displaying C1 and C4 or playback ofmp3 files from C2. In FIG. 21, if UD2 moves 2133 out of RF range ofmedia device 100, C2 may be released from the queue and action on C2 maystop and the next item of content in the queue is acted on (e.g., C3).FIG. 21 is a non-limiting example and nothing precludes one of the userstaking action to change the queuing order or the order in which themedia device acts on queued content. Moreover, CFG 125 and/or APP 225may be used to determine content queuing and an order in which queuedcontent is acted on by media device 100. One of the users may have superuser capability (e.g., via that user's APP 225 and/or CFG 125) thatallows the super user to override or otherwise control content handlingon media device 100.

FIG. 22 depicts another example 2200 of a media device handling,storing, queuing, and taking action on content from a plurality of userdevices. Here, a plurality of users 2200 a-2200 n have approached mediadevice 100 and have be detected by a proximity island 520. A pluralityof user devices UDa-UDn, having content Ca-Cn, are in wirelesscommunications 2167 as described above. In diagram 2280, the contentCa-Cn from the user devices is queued in the order the user devices weredetected by media device 100. Content Ca-Cn may be stored and/oraccessed by media device 100 from any location that may be directlyaccessed or wirelessly accessed by media device 100 such as in DS 103(directly accessed), NAS 2122, the user devices UDa-UDn, the Cloud 2250,etc.

Media device 100 may take action on the queued content in any orderincluding but not limited to random order, the order in which it isqueued, or commanded order, just to name a few. Media device 100 may beconfigured to operate in a “party mode” where each of the users 2200a-2200 n in proximity of the media device 100 desires to have theircontent played back on the media device 100. Media device 100 mayharvest all of the content and then act on it by randomly playing backcontent from Ca-Cn, allowing one of the users to control playback, likea DJ, or allowing a super user UDM to control playback order and contentout of Ca-Cn. One of the users may touch or otherwise actuate one of thecontrol elements 503-512 and/or one of the proximity detector islands520 or an icon on DISP 180 to have their content acted on by mediadevice 100. Content in Ca-Cn may be released by media device 100 if theuser device associated with that content moves out of RF range of themedia device 100.

In FIG. 23, a flow 2300 for recording user content on a media devicewhile the media device handles current content is depicted. At a stage2302 entry of a user (e.g., hand of a user) into detection range of aproximity detection island 520 of media device 100 is detected. At astage 2304 the user is notified that media device 100 has detected theuser's presence (e.g., using light, sound, vibration, etc.). At a stage2306, media device 100 may use RF system 107 to detect RF signals beingtransmitted by a user device (e.g., 220) as described above. At a stage2308, the media device 100 and the user device wirelessly connect witheach other (e.g., using WiFi 130 or BT 120). At a stage 2310 contentcurrently being handled by media device 100 (e.g., being played back orqueued for playback) is displayed on the media device 100 (e.g., DISP180) or on a display of the user device, or both, for example. APP 225or other software and/or hardware may be used to display the currentcontent being handled on media device 100 on the user device. At asstage 2312, a request from the user device to the media device 100 forthe media device 100 to handle user content from the user device isreceived. At a stage 2314, the media device 100 harvests the usercontent from the user device (e.g., wirelessly copies, streams, orotherwise accesses the user content). The user content may reside on theuser device or may be located elsewhere at a location the media device100 or user device may access, such as the Cloud, the Internet, anintranet, NAS, or other, for example. At a stage 2316 the media device100 begins recording the user content while continuing playback of thecontent currently being handled by the media device 100. As wasdescribed above in reference to FIG. 22, the media device 100, based ona size of the user content (e.g., file size in MB or GB) may record theuser content to memory internal to the media device 100 or to a locationexternal to the media device 100 (e.g., NAS, the Cloud, a server, theInternet). Content that was being handled by the media device 100continues with little or no interruption while the user content isrecorded. At a stage 2318 the user content is stored as described aboveand flow 2300 may terminate at the stage 2318. Optionally, at a stage2320, a determination may be made to queue the user content relative tothe current content being handled by the media device 100. If no queuingaction is to be taken, then a NO branch may be taken and the flow 2300may terminate. However, if the user content is to be queued, then a YESbranch may be taken to a stage 2322 where a queuing action is applied tothe user content. Queuing action may mean any action taken by the mediadevice 100 (e.g., via controller 101, CFG 125, hardware, or software)and/or user device (e.g., via APP 225) that affects the queuing ofcontent on the media device 100.

Queuing action may include but is not limited: to waiting for the usercontent to complete recording and then placing the user content in aqueuing order relative to other content already queued on the mediadevice 100 (e.g., at the back of the queue); bumping content presentlyat the front of the queue once the user content has completed recordingand beginning playback of the recorded user content; placing the usercontent behind the content currently being handled by the media device100 such that the user content will be next in line for playback; movingthe user content to the front of the queue; randomly placing the usercontent in the queue; allowing the user of the user device to controlthe queuing of the user content; allowing a DJ or other user to controlthe queuing of the user content; and allowing each user that is detectedby the proximity detection islands, have one or more items in theircontent harvested and pushed to the top of the queue or placed next inline in the queue; and placing the user content in a queue deck withother content, shuffling the deck and playing on of the items of contentfrom the deck, and re-shuffling the deck after playback of item; just toname a few.

Content, including the user content that was recorded may be queued in aparty mode where each user who wants their content played back on themedia device 100, approaches the media device 100, is detected by theproximity detection islands, receives notification of detection, has atleast one selected item of user content harvested by the media device100, and has the item of user content played back either immediately orafter the current content being played back finishes. In some examples,the queue for content playback on media device 100 is only two items ofcontent deep and comprises the current piece of content being playedback and the user content of the user who approached the media device100 and had their content harvested as described above.

Now referencing FIG. 24, one example 2400 of queuing action for usercontent in a queue of a media player is depicted. In example 2400 thereare at least seven users U1-U7 and at least seven user devices UD1-UD7.For purposes of simplifying the description, assume that all seven usershave approached media device 100, have been detected 2140 and notified2117 by proximity island 520, and all user devices have been detectedand wirelessly connected with media device 100. Here user content C1,C2, and C3 has been queued in queue 2480 and DISP 180 is displaying thequeued order of the playlist as Song for UD1 currently being played backbecause it is underlined (e.g., over SPK 160), with Songs for UD2 andUD3 being next in the playlist. User content for UD1-UD3 may reside inDS 103 or other location such as NAS 2122 or Cloud 2250. User devicesUD1-UD3, in that order, were the first three devices to wirelesslyconnect and have their user content C1-C3 harvested by media device 100.The Action for the queuing order in queue 2480 is “Play In Order”, so C1is first, C2 is second, and C3 is third in the playback order asdisplayed on DISP 180. At some point in time, UD7 also wirelesslyconnected and had its user content C7 harvested by media device 100.Media device 100 begins the process of recording 2490 the content intoDS 103 (e.g., into Flash 145). In the meantime, other user devices (notshown) may also have their user content harvested. In that the recording2490 of C7 is still in progress, intervening user content will be placedahead of C7 until C7 has completed 2492 recording 2492. Upon completionof recording, C7 is positioned 2482 in the playlist below some alreadyqueued user content and ahead or other user content lower in the queue.In other examples, C7 may be queued in the order it was presented to themedia device 100 and the media device 100 begins the recording 2490process and allows C7 to be played back when it moves to the top ofqueue, but if C7 has not completed recording 2492, then media device 100begins the playback 2493 of C7 from a buffer BUFF 2421 where a portionof recorded C7 is stored. The playback from BUFF 2421 may continue untilthe recording catches up with the buffered content or is completed 2492.

As described above, one of the users or user devices may have super user(e.g., UM) or other form of override authority and that user may orderthe queue to their liking and control the order of playback of usercontent. Queue 2480 and/or the user content being queued need not residein memory internal to media device 100 and may be located externally inNAS 2122, a USB Hard Drive, Cloud 2250, and a server, just to name afew. In some examples, media device 100 may delete or bump user contentfrom queue 2480 if the wireless connection 2167 between media device 100and the user device is broken or interrupted for a predetermined amountof time, such as two minutes, for example. The “Play In Order” exampledepicted is a non-limiting example and one skilled in the art willappreciate that the queuing may be ordered in a variety of ways and maybe determined by executable program code fixed in a non-transitorymedium, such as in DS 103, Flash 145, CFG 125, and APP 225, just to namea few. Therefore, controller 101 or a controller in a user device mayexecute the program code that determines and controls queuing of usercontent on the media device 100.

Although the foregoing examples have been described in some detail forpurposes of clarity of understanding, the above-described conceptualtechniques are not limited to the details provided. There are manyalternative ways of implementing the above-described conceptualtechniques. The disclosed examples are illustrative and not restrictive.

What is claimed is:
 1. A method for proximity-based control of contentpresented on a device, comprising: detecting presence of a user within adetection range of one or more of a plurality of proximity detectionislands of a media device, each proximity detection island is disposedproximate to a corner of a top surface of the media device ; notifying,using one or more colors of light generated by one or more of theplurality of proximity detection islands, presence has been detected ;detecting a RF signal from a user device; connecting wirelessly, theuser device and the media with each other; displaying content currentlybeing handled by the media device; receiving at the media device, arequest from the user device configured to cause the media device tohandle user content on the user device; harvesting wirelessly the usercontent from the user device; and recording the user content whilecontinuing to handle content currently being handled by the mediadevice.
 2. The method of claim 1 and further comprising: queuing theuser content relative to the content currently being handled.
 3. Themethod of claim 1, wherein the queuing occurs after the recording iscompleted.
 4. The method of claim 1, wherein the recording is stored inmemory internal to the media device.
 5. The method of claim 1, whereinthe recording is stored at a location external to the media device. 6.The method of claim 1, wherein the displaying occurs on the mediadevice, the user device, or both.
 7. The method of claim 1 and furthercomprising: queuing, preferentially, the user content relative to thecontent currently being handled.
 8. The method of claim 1 and furthercomprising: modifying a playlist on the media device in response to therecording.
 9. The method of claim 8, wherein the modifying is by themedia device.
 10. The method of claim 1, wherein the handling comprisesplayback of the content currently being handled.
 11. A wireless device,comprising: a controller in electrical communication with a data storagesystem, a radio frequency (RF) system including at least one RF antennaelectrically coupled with a plurality of RF transceivers including aWiFi transceiver, a Bluetooth (BT) transceiver, and an ad hoc (AH)transceiver, an audio/video (AN) system including a loudspeakerconfigured to produce sound, a microphone configured to capture sound,and a display configured to display information, a plurality ofproximity detection islands, each proximity detection island is disposedproximate to a corner of a top surface of the wireless device, and eachproximity detection island is configured to wirelessly detect, using anambient light sensor, presence of a user and configured to notifypresence has been detected using one or more colors of light generatedby a light emitting diode, wherein the RF system is configured to detecta RF signal from a user device, to wirelessly connect with the userdevice, wirelessly access user content from the user device or alocation specified by the user device, and wherein the controller isconfigured to record the user content in the data storage system or inan external location that is wirelessly accessible using the RF system,and configured to handle current content from a content queue while theuser content is being recorded.
 12. The device of claim 11, wherein thehandling comprises playback on the A/V system of the current content.13. The device of claim 11, wherein the user content is recorded intoFlash memory.
 14. The device of claim 11, wherein the controller isconfigured to queue the user content into the content queue.
 15. Thedevice of claim 11, wherein queuing of the user content by thecontroller is determined by a party mode.
 16. The device of claim 11,wherein a portion of the user content is buffered into a buffer duringthe recording.
 17. The device of claim 16, wherein the portion of theuser content in the buffer comprise the current content.
 18. The deviceof claim 17, wherein the current content is played back using the AVsystem while the user content is being recorded.